![]() ![]() NET Framework 4.6 or newer, no additional action is required to support TLS 1.2. NET developers do?įirst, ensure you have the latest Autodesk Forge package version, currently 1.2, which includes fixes and improvements. In our case, as we're using RestSharp, actually the app needs to add support, not the packages (sorry being redundant here, just reinforcing the point). The application & packages will run using the .NET version of the project. NET object, so the actual connection is a system feature. The second is the most restrictive in terms of supported versions, so that's what we use, see their summary here. RestSharp is not recreating the base connection, it uses HttpWebRequest. NET Core).īut why these versions? The Forge package relies on 2 other packages: Newtonsoft.JSON & RestSharp. NET Framework 4.5.2 and, more recently, started supporting. NET framework apps.NET Framework 4.5 Support NET 4.5 Framework developersįollow started with this previous blog post for basic information, this article will just summarize actions for. NET version (like 4.0 or 4.5) which may be the cause? After all, the total Excel Add-in that I built is my DLL (.NET 4.8) and your DLLs (.NET 4.TLS 1.2 for. Hence my question: Is Add-in Express perhaps compiled with (or targets) a lower. I just don't understand what the problem is and why what I experience conflicts with everything that microsoft recommends. NET 4.8 should not require code or registry changes.īut when running the Excel plugin it does require one of these changes. Using SecurityProtocolType.SystemDefault does NOT work, which is the actual strange part, since using Win10 +. Your suggestion to set ServicePointManager.SecurityProtocol to SecurityProtocolType.Tls12 works, but goes against what microsoft recommends. "TLS 1.2 support: Supported, and enabled by default." NET 4.8, TLS 1.2 should be enabled by default: What I just don't understand is that, when I compile with and target. ![]() Using SecurityProtocolType.SystemDefault is not an option because what you said, at the highest TLS 1.0 is offered. I also do not want to give clients instructions to set registry keys since we security should be standard, not opt-in. PS I do not want to set ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 in my code since Microsofts explicitly says not to tie your code to a protocol. NET 4.0.Īnd (I am now assuming) that this may very well cause the TLS problems. ![]() ![]() I checked with dotPeek and dotPeek reports that AddinExpress.XL.2005.dll is compiled with (or runs). Is it possible that the Addin Express is compiled with (or targets). NET 4.5 or lower is used for running the code. When checking ServicePointManager.SecurityProtocol the values are Ssl3 and Tls, which are strong indicators that. NET 4.8 in our plugin TLS 1.2 is not supported. NET 4.8, which according to Microsoft ensures that TLS 1.2 is supported without any code or registry changes:īut it isn't. NET framework does not support the TLS 1.2 protocol and cannot fallback to lower (unsecure) protocols. On the webserver we reconfigured to only allow TLS 1.2 and suddenly the HTTP Requests do not work anymore with this WebException: The underlying connection was closed: An unexpected error occurred on a send. I have an Excel Add-in, which does HTTP REST calls and transforms the output to ranges in the current workbook. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |