ASP.NET 3.5 is getting pretty old and the ideal solution would be to update to the latest ASP.NET version but let’s face it, there are some legacy systems already running 3.5 that are not easy to upgrade and most external services are closing support for the depreciated TLS 1.0 and TLS 1.1 protocols.
I searched for solutions online and most replies were indicating that there was no TLS 1.2 support in ASP.NET 3.5 and it would not be supported which is not true.
Microsoft released upgrade a while ago which added TLS 1.2 support for ASP.NET 3.5. Chances are that you already have it installed on the server but if not, you can download it here. If you get the error: “The update is not applicable to your computer.” it’s probably already installed. Continue reading
If you have a assembly with the same version number located both in the bin folder for a web site and in the Global Assembly Cache (GAC), ASP.NET will by default use the GAC version of the file. Sometimes that’s not the ideal solution so here’s a workaround.
1. Open web.config in a text editor
2. Add this code to /configuration/runtime/assemblyBinding/dependentAssembly:
<assemblyIdentity name="Your.Assembly.Name" publicKeyToken="31bf3856ad364e35"/>
<codebase version="188.8.131.52" href="/bin/Your.Assembly.Name.dll" />
Below are instructions on how to encrypt a string using a private key. The encryption will be reversible if you got the private key.
To encrypt use this command:
aiplib.Crypt crypt = new aiplib.Crypt();
string encrypted = crypt.Encrypt("privatekey", "value");
When uploading files greater than 28.6 MB (30000000 Bytes) with ASP.NET on IIS 7.5 using SWFUpload I’m getting this error:
There has been an I/O Error: Error #2038