Microsoft has presented an interesting project named Roslyn. Within the framework of this project, all the concept of compilers and compilable programming languages itself has been reconsidered. Apart from the realization of completely new functions, such as .NET-tools, C#, Visual Basic and the Visual Studio development environment, the Roslyn project offers the completely new concept ‘compiler as a service’, laying a road to the .NET platform to the most promising area – into clouds.
Once Microsoft gave many professional software developers the hope for well-off and predictable future, having moved the development of its own and third party technologies on the .NET development platform.
The Roslyn technology can be described as ‘compilation by request through the providing service’, although this description is a bit complicated. Technically, the new technology is not a service in comparison with such cloud solutions as SaaS (Software-as-a-Service) or PaaS (Platform-as-a-Service). The Roslyn technology is more similar to the Windows system services that offer completely new principles of compiling .NET applications – each phase of compilation is presented in the form of service that can be requested by other applications.
Usual compilers throw away all intermediate data while getting ready-made files and in Roslyn compilers all intermediate data is available via standard .NET API-interfaces. For example, the request to one single API will retrieve the whole syntax tree for the given code fragment in the form of an object. The request to another API can return the number of methods in code.
So far, one can’t predict how soon the Roslyn technology will find its place among standard development tools – now only the trial version for C# and Visual Basic is available.