News for hackers. Stuff that matters.

A comment on Microsoft previews Roslyn: .NET Compiler-as-a-Service infrastructure. Parent comment

Re:Microsoft previews Roslyn: .NET Compiler-as-a-Service inf... by solutionyogi on Wednesday October 19, 2011 @11:37PM (#3133339)
Roslyn will be good. It has to be because from what I understand, the MS team themselves will use Roslyn in Visual Studio and other products. Roslyn isn't just a public API for others to analyze code. It will be the foundation on which .NET framework languages will depend upon.

See Eric Lippert (Member of the Roslyn team, C# Principal) notes here:

http://blogs.msdn.com/b/ericlippert/archive/2011/10/19/the-r...

[ Parent | on HN ]
Re:Microsoft previews Roslyn: .NET Compiler-as-a-Service inf... by SeveredCross on Thursday October 20, 2011 @12:25AM (#3133447)
Well…I think Roslyn will be good, but I think it's reaching to say it must be because the MS team themselves will use it.

After all, these are the same people who invented (and used!) MFC, long known as the Microsoft Frustration Classes.

[ Parent | on HN ]
Re:Microsoft previews Roslyn: .NET Compiler-as-a-Service inf... by xpaulbettsx on Thursday October 20, 2011 @01:04AM (#3133528)
1992 called and wants its Microsoft stereotype back.
[ Parent | on HN ]
Re:Microsoft previews Roslyn: .NET Compiler-as-a-Service inf... by SeveredCross on Thursday October 20, 2011 @01:16AM (#3133554)
It was a joke, lighten up. For what it's worth, I'm a .NET developer and think it's awesome.
[ Parent | on HN ]
Re:Microsoft previews Roslyn: .NET Compiler-as-a-Service inf... by solutionyogi on Thursday October 20, 2011 @04:04AM (#3133933)
Well, MFC was actually a library. And I know it was a poor library. But this is a different ball game.

With Roslyn, they are going to write C# compiler in C# itself (and VB compiler in VB). And if they expose this as an API, it's guaranteed that I will be able to parse every valid C# file.

[ Parent | on HN ]