AWS SDK version 3 about justsaying HOT 10 CLOSED

I had a look at their commits and couldn't find any change to SNS SQS clients since version 2.3.x. https://github.com/aws/aws-sdk-net/commits/master

from justsaying.

So this suggests that the update to AWS SDK 3.x should be a) easy, but b) not that useful until we look at DotNet Core ?

from justsaying.

@AnthonySteele Is there any benefit to update the SDK right now? Or should we update when we're looking at DotNet Core?

from justsaying.

It would be pro-active to update to AWSSDK 3.x soon, it will be necessary when we look at DotNet Core.

from justsaying.

One subtle advantage you might find in 3.1.x version of the AWS SDK for .NET is we no longer update the AssemblyVersion for every release. It is currently locked to version 3.1 and 3.2 for the coreclr beta release. This was done to help class libraries like this not need to do a recompile for every new release of the SDK. The AssemblyFileVersion is still always updated for every release but that version is just for display purposes.

from justsaying.

That is very useful @normj. Thanks for that.

from justsaying.

in AWS Blog it is said no more new features will after 8/1/2016, only critical issue fixes for v2.

There's a nice migration guide here. I understand if we first update to latest AWS v2 SDK, and solve all warnings, transition to v3 should be smooth.

from justsaying.

I did a pullrequest for this: #209, correction #210 this time from the company account

from justsaying.

👍 great. We will look at trialing and merging this after the next release

from justsaying.

Fixed in v5 rc1

from justsaying.