This is AWESOME! I saw Anders demoing Roslyn at //BUILD. It was very cool to see him take code compiled in C# and re-generate VB.NET from it ... and vice-versa.
Having a full-fidelity CaaS will unlock a number of opportunity in dev tooling, IoC and DI container implementation, etc., logging/tracing tools, AOP scenarios, etc.
Can't wait to free up a few cycles to go pound on this
Microsoft officials said at the Build conference that Microsoft would release a Community Technology Preview (CTP) test build of its “Roslyn” compiler as a service technology in October.
On October 19, Microsoft made good on that promise, and posted the Roslyn bits on its Download Center.
Microsoft officials wouldn’t provide a tentative ship timeframe for Roslyn at the Build show, but after viewing the slides from a presentation there, I predicted Roslyn wouldn’t be part of the next release of Visual Studio, which is coming in 2012.
Microsoft confirmed today that Roslyn is a post-Visual Studio ‘11 (Visual Studio 2012) deliverable. From a note on the download:
“‘Roslyn’ CTP installs as an extension to Visual Studio 2010 SP1. ‘Roslyn’ is a long lead project which we are considering for the post-Visual Studio 11 timeframe. The CTP includes an early preview of the APIs exposed by the C# and Visual Basic compilers, and the Interactive window experience.”
A quick Roslyn refresher: The Roslyn effort is about re-architecting the C# and VB compilers to support “compiler as a service” (CaaS) scenarios. Currently, a compiler is a black box; with Roslyn, Microsoft is working on opening it up so that all of the information processed via a compiler is available in application programming interface (API) form.
