Geek Answers Handbook

Why are so few .NET languages ​​integrated in Visual Studio (in particular, VS2008)?

The "core" .NET languages ​​are integrated into VS2008 - C #, VB.NET and C ++. I am not sure about the current support for J # and JScript.

But there are several other .NET languages: A #, Boo, Oxygene, F #, IronLisp / IronScheme, IronPython, IronRuby, Nemerle, Phalanger, P #, PowerShell and more . Of these, I only found VS support for F # (which is made by Microsoft, therefore not surprisingly), Oxygene, A # (but only VS2005 support) and IronPython (only for external projects designed for this purpose).

But what about other languages? Since they are aimed at the .NET runtime, I believe that it only makes sense to use these languages ​​inside VS. Are there some limitations of Visual Studio that prevent this? Is there a way to “force” VS to compile these languages?

+5
source share
3 answers

, : IDE - , . , , . - - , Visual Studio , - .

, , , , , "" , .

Boo, , BooLangStudio.

+7

. , VS ( , intellisense, squiggles) ( , , , MSBuild), , MPF.

+3

, , VS . , , , .NET. , ( ​​ ) , Ruby, PHP Classic ASP.

Another question: why VS'08 cannot open and save solution / project files that can be opened and saved in VS'05 ??

0
source

More articles:


All Articles