Backward Compatibility of .NET Compiler Platform Preview for Visual Studio 2014

Topics: APIs, C# Language Design, VB Language Design
Jun 17, 2014 at 8:22 PM
I'm using .NET Compiler Platform (Roslyn) Preview for Visual Studio 2013, I recently noted that there is some notable changes in the same after getting the latest references from NuGet.

I'm developing a tool that will be made available in VS2013 in our office development machines. By introducing a new set of API my development be in vain if its only available for VS2014.

Is there any confirmation from Microsoft about VS2013 about backward Compatibility.
Jun 17, 2014 at 9:43 PM
You might find reply to useful.
Jun 18, 2014 at 2:35 AM
I wanted to know if support for VS2013 will be completely removed.
Jun 18, 2014 at 5:45 PM
As Pilchie said, we are currently focused on VS 2014 and have no plans to support VS 2013 going forward. Future releases of Roslyn will not be compatible with VS 2013.
Marked as answer by TomasMatousek on 8/3/2014 at 12:00 AM
Jun 18, 2014 at 6:38 PM
So, will it be like that the VS2013 version will be kept untouched so that people who have already implemented tools out of it can still use it, and further enhancement developments will continue in VS2014.

Is it okay to presume that Roslyn compilers that were used for VS2013 preview can be used for compiling production codes, or would you advice to do the final compiling with native compiler. Hopefully the switching is not hard, since there is a huge investment already made in procurement of VS2013, porting our codebase to .NET 4.5 while dealing with third party APIs and making IDE tools out of Roslyn VS2013 preview.
Jun 18, 2014 at 10:48 PM
I don't think there's a go live license for any of Roslyn's stuff.
Aug 12, 2014 at 4:40 PM
I'm not clear on this topic. Is it safe to say that the compilers are on par with the native. I know these are the compilers used in VS2014, but is it adviced to only use Roslyn for experimental purposes for VS2013.