(Replacing message template with parser tag) |
No edit summary |
||
Line 1: | Line 1: | ||
<message>Write the content here to display this box</message> | <message>Write the content here to display this box</message><html> | ||
<div class="outdated-alert"> | |||
<p> <span> ❗🕜 Warning: </span> this article may contain outdated information. Consider before using any descriptions/solutions, otherwise, it can still be helpful. <a href="https://learn.mdriven.net/index.php/MDriven_Product_Line#Synonyms_and_name_changes"> <span> Help: Synonyms and name changes </a> | |||
</p> | |||
</div> | |||
</html> | |||
==== 2018-07-11 ==== | ==== 2018-07-11 ==== | ||
The core assemblies of MDriven (Eco.Handles and Eco.Interfaces) were updated from .net4 to .net4.5 | The core assemblies of MDriven (Eco.Handles and Eco.Interfaces) were updated from .net4 to .net4.5 |
Latest revision as of 06:29, 21 June 2024
❗🕜 Warning: this article may contain outdated information. Consider before using any descriptions/solutions, otherwise, it can still be helpful. Help: Synonyms and name changes
2018-07-11
The core assemblies of MDriven (Eco.Handles and Eco.Interfaces) were updated from .net4 to .net4.5
The main reason was the Transport Layer Security protocol (TLS) that replaced the legacy SSL protocol. TLS is in Azure, now defaulted to TLS1.2, and for us to support that, we need .net Framework 4.5
You may experience compilation errors if your solutions compile with .net versions older than 4.5
To fix this, update the .net Framework version to at least 4.5 on your projects.
If you write code that suddenly does not want to connect with MDriven over HTTPS, then consider adding this initialization:
System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;