17 April, 2014

Keeping an Eye on Rosyln

Over the past few days there has been a bit of news about Roslyn. I am working on getting my head around what is Roslyn and why do I care?

What is Roslyn?

"The .NET Compiler Platform ("Roslyn") provides open-source C# and Visual Basic compilers with rich code analysis APIs. You can build code analysis tools with the same APIs that Microsoft is using to implement Visual Studio!" - http://msdn.microsoft.com/en-us/roslyn

The way I am understanding this is Roslyn allows the C# code to help write C# code. A few others has commented that Roslyn would allow for the scripting of code plus the ability to compile/execute that code on the fly. 

Should I care about Roslyn?

The short answer is yes. 

Roslyn holds the promise of changing the way code is written, the way code is refactored, and the way code is analysed. 

It seems to me that the inline declaration expressions will take a little getting use to and will help produce more readable code.

I am rather excited to see what new features and tools people will develop to help with refactoring code. The example, I see the most showing off Roslyn's refactoring capabilities is the inline rename. 

It seems to me that Roslyn can help with Aspect Oriented Programming (AOP). In the AOP world, logging is the use case people point to for the need of AOP. Logging is common utility that is needed through out a program. It can get rather ugly and boring to write a logging statement in each method. It would be great to have a tool, script or the compiler automatically add logging to each method and to not clutter up the code with logging statements.

References


No comments:

Challenging myself to learn something new

I have recently set a big challenge for myself. I want to know about Machine Learning . To add to the challenge, I am trying out usin...