.net-4.6

After recently upgrading to .net 4.6 we discovered a bug where RyuJit produces incorrect results, we were able to work around the issue for now by adding useLegacyJit enabled="true" to the app.config. How can I debug the machine code generated by the following? I created a new console project in VS 2015 RTM, set to Release, Any CPU, unchecked Prefer 32 bit, running with and without debugger attached produces the same result. using System; using System.Runtime.CompilerServices; namespace ConsoleApplication2 { class Program { static void Main(string[] args) { Console.WriteLine(Calculate());

I upgraded to Visual Studio 2015 from our MSDN subscription because I was pretty excited to read about Shared Projects... No more managing 21382 nuget packages in our dependencies when all we want to do is reuse code. So I built a test shared project with some code in it. Then I add a new empty web application on .Net 4.6 to the project. Now I expected to go to references and see a "Shared Projects" tab on the references window, but I do not see one. Now I can add a class library to the same solution and I see the tab and can add the shared reference. However I cannot add the shared project to

According to .net guidance of TLS protocol programming , it suggests to config security via appcontext switch when your project targets on .net 4.6. This way works when add appcontext in app.config for console application. However, it doesn't work when add appconext switch in web.config for website project. This is the config I add. <runtime> <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false;Switch.System.Net.DontEnableSystemDefaultTlsVersions=false"/> </runtime> AppContext switches usage in web config file: <appSettings> <add key="AppContext.SetSwitch

I am using Visual Studio 2015 Enterprise RTM to write unit tests for a project that uses Unity Container . I have discovered that the simple act of adding a fakes assembly for Unity, not even actually using the fake, is sufficient to generate this exception: System.InvalidProgramException: Common Language Runtime detected an invalid program. Consider the following steps to reproduce: Using Visual Studio 2015 Enterprise RTM create a Unit Test project targeting .NET 4.6 Add the NuGet package "Unity" version 3.5.1404.0 Add the NuGet package "CommonServiceLocator" version 1.2.0 Write a single unit

Summary : In a library method, when should I use the async and await keywords instead of returning a Task directly? I believe my question is related to this one . However, that question is about .NET 4.0 and the TPL, while I'm using .NET 4.6 with the async and await keywords. So, I think my question might get different answers because these keywords didn't exist when the linked question was answered. Explanation: I'm writing a simple wrapper for an external WCF service and the wrapper makes multiple SendAsync calls. Now I think that each wrapper method should just return a Task<> directly