= 12įinally, if your app is running an older version, it's probably not using RestSharp (requires 4.5.2), but still possible to support TLS 1.2 using this workaround, but you need to check how the actual connection is performed. NET 4.5.2, you'll need to add the following global change, preferably at the entry point and before any REST request. It's worth noting that 4.6 is almost 4 years old now, a lot has happened since its launch. Great news! If your app is running an older version, consider migrating to this version (or even newer). NET Framework 4.6 or newer, no additional action is required to support TLS 1.2. 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).įirst, ensure you have the latest Autodesk Forge package version, currently 1.2, which includes fixes and improvements. 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. Follow started with this previous blog post for basic information, this article will just summarize actions for.
0 kommentar(er)
