As you may know, the payment card industry is moving quickly to adopt TLS 1.2 and get rid of less secure protocols.[1] To this end, Authorizet.Net has turned off TLS.1.2 on its sandbox environment as of April 30, 2017. [2]
The curious part about this change is how it impacts the developer world. We have some older projects built using VS2010 (msbuild) and old web deploy projects. Up until April 30, we could build those with .NET 4 and VS2010. So we happily and blindly did that, until May 1.
Starting May 1 we started to see those pesky communication disconnection errors. Darn, what is that? Well, that's the TLS 1.2 requirement in sandbox. So we apply the fix and discover that .NET 4 does not have the TLS 1.2 enum SecurityProtocolType. Well, double bummer.
When we move on to .NET 4.5.1 to get that SecurityProtocolType.Tls12 we discover that we can no longer use VS2010 msbuild. Why? Because that old VisualStudios can't build .NET 4.5.1. [3] How fun is that?
With one change from an unrelated industry our development environment will be forced to phase out anything prior to VS2013, and thus all web deploy projects. Now we have to adopt a different web application build workflow. I am sure we are not alone.
There are alot of developers who resist migrating to newer versions of VS. I remember one guy who was adamant that VS2010 was the best IDE ever built by Microsoft and tried everything to keep it working. We only keep it around for the old web deploy projects for some apps that are huge.
Hasta la vista, baby!
[1] http://help.theatremanager.com/frequently-asked-questions/june-2016-use-tls-11-and-authorizenet
[2] https://github.com/AuthorizeNet/sdk-php/issues/222
[3] http://stackoverflow.com/questions/12390175/targeting-net-framework-4-5-via-visual-studio-2010
The curious part about this change is how it impacts the developer world. We have some older projects built using VS2010 (msbuild) and old web deploy projects. Up until April 30, we could build those with .NET 4 and VS2010. So we happily and blindly did that, until May 1.
Starting May 1 we started to see those pesky communication disconnection errors. Darn, what is that? Well, that's the TLS 1.2 requirement in sandbox. So we apply the fix and discover that .NET 4 does not have the TLS 1.2 enum SecurityProtocolType. Well, double bummer.
When we move on to .NET 4.5.1 to get that SecurityProtocolType.Tls12 we discover that we can no longer use VS2010 msbuild. Why? Because that old VisualStudios can't build .NET 4.5.1. [3] How fun is that?
With one change from an unrelated industry our development environment will be forced to phase out anything prior to VS2013, and thus all web deploy projects. Now we have to adopt a different web application build workflow. I am sure we are not alone.
There are alot of developers who resist migrating to newer versions of VS. I remember one guy who was adamant that VS2010 was the best IDE ever built by Microsoft and tried everything to keep it working. We only keep it around for the old web deploy projects for some apps that are huge.
Hasta la vista, baby!
[1] http://help.theatremanager.com/frequently-asked-questions/june-2016-use-tls-11-and-authorizenet
[2] https://github.com/AuthorizeNet/sdk-php/issues/222
[3] http://stackoverflow.com/questions/12390175/targeting-net-framework-4-5-via-visual-studio-2010