Preparing 104.2.0 release

[haacked]

TODO

• Update the version to remove pre-release
• Write a blog post
• Merge to master
• Tag the release
• Create the release
• Publish to NuGet

[devinrader]

Do you think we should modify the nuget package to add a binding redirect for RestSharp? I know we've run into issues in the past where the Twilio library needs version X of restsharp, but RandomOtherPackage installs version Y and now we break.

From what I've read, it seems like having RestSharp add a binding redirect might help avoid that issue.

[haacked]

Do you think we should modify the nuget package to add a binding redirect for RestSharp?

Huh? I RestSharp is not strong named so no binding redirects are necessary or even possible. Also, NuGet does that automatically anyways, so there's nothing to do within the package.

Do you need RestSharp to be strongnamed?

[devinrader]

OK. Honestly my knowledge around assembly versioning is limited, I just know that customers have in the past had the issue I described.

No strong naming please.

[haacked]

No strong naming please

Ha! I just reopened an issue to consider it. #216

There have been some new approaches to doing it that make a lot of sense. :)