The new programming languages have nothing to do with VS.NET, just as C++ has nothing to do with VC++ 6. There are countless resources on the NET to learn about .NET, and the languages it ships with - gotdotnet.com being a good place to start.
This review only scratches the surface of what you can do with VS.NET, but I'm very surprised Debugging got only an 86%, and Extensibility only got an 87%!
VS.NET has the coolest debugging abilities I've ever seen, including the ability to seamlessly debug across different languages, processes, and even entire machines.
I can debug an SQL stored procedure (yes, debug... as in with watch variables, a mouse-over value displays) that resides on a server anywhere on the Internet, that is exposed via a Web service written in VB.NET, which is access from a client application written in C#. So I'm traversing 3 different languages, 3 different processes, and 2 (or more!) physical machines... all by setting a break point. What more do you want? Fried chicken to come out of your printer!?
As far as extensibility, I can create VS.NET extension right inside VS.NET with a VS.NET Component project. I've seen some *awesome* VS.NET extensions, especially the ones from Rational software, which are incredibly complex applications embedded directly inside VS.NET, and integrated seamlessly with the existing tools.
Not to mention the fact that 3rd parties can write entirely new languages (or support for older ones) that will all work within VS.NET as first class citzens! So I can write/debug Eiffel.NET (RMD.NET, for that matter!) code inside VS.NET just like I can write/debug C#.
The only issues I've had with VS.NET are ones that revolve around group projects that deal with multi-file assemblies. Alas, VS.NET doesn't support multi-file assemblies right now... so it makes it difficult to work with them. I've also had some issues with dependencies and deployment... but they were minor and easy to work around.
Other than that, VS.NET rocks my world. It's a 95% in my book... if not better.
|