You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VS2015 documentation does not include any section on breaking changes in the languages or compilers, even though there are many changes as the compilers were rewritten from scratch.
After switching to Visual Studio 2015, we have noticed that some changes made to how lambdas are compiled to MSIL in Roslyn (described in this thread and on GitHub) introduce runtime failures under certain conditions.
Since Roslyn is obviously the future of .NET, we would like to switch to this technology, but it seems that all legacy code which has been running in production (and where we have a fair degree of confidence it works correctly) is now prone to new runtime failures. These are several libraries which are impacted by this issue also (like Moq, for example).
We already skipped the upgrade to RyuJIT for its issues, but I believe Visual Studio 2015 is heavily integrated with Roslyn and I don't think we can simply replace the csc.exe manually (but that's a different question).
So, is there a compiled list of breaking changes in Roslyn which we could reference to see what we can expect?
There are now breaking changes documents in the Roslyn repository under docs/compilers
The VS2015 documentation does not include any section on breaking changes in the languages or compilers, even though there are many changes as the compilers were rewritten from scratch.
From stackoverflow:
There are now breaking changes documents in the Roslyn repository under docs/compilers
Many more items need to be copied from our internal "compiler specification".
The text was updated successfully, but these errors were encountered: