5 ms·
Is there anything new in Visual Studio 2010?
- citizenparker 17y agoIt's a shame the author isn't really distinguishing between Visual Studio 2010 and v4 of the Common Language Runtime / Dynamic Language Runtime. VS 2010 has some neat integration points but isn't really of interest to the HN community - an in-depth look at v4 (particularly the DLR) however is worth chatting about sometime.
- AndrewDucker 17y agoTo be honest, what I'm looking forward to most in VS2010 is the revamped IDE, and particularly the Call Heirarchy feature - which shows you the heirarchy of everything your method calls into (and vice versa).
- bep 17y agoThe IDE is redesigned and now uses WPF. Also, the Historical Debugger sounds intriguing.
- dmlorenzetti 17y agoOliveira's "new features in Visual Studio" are all programming languages it now supports-- in other words, the development environment is synonymous with the compilers bundled with it. When I left Windows as a development platform (maybe 10 years ago), it took a while to appreciate how deep the Unix philosophy of "compact, orthogonal tools" really runs. Now, though, it would never occur to me to describe a new compiler as a "feature" of the other tools I use. I'm not sure that the difference in worldview really matters. I doubt that I'm significantly more productive now than I was with Visual Studio. However, I do feel incredibly straightjacketed whenever I have to go back to VS, as if that monolithic view of software is imposing itself on me, rather than letting me do what I want as I want.
- wglb 17y agoIt seems like adding features often reduces functionality or utility.
- rbanffy 17y agoVS is required to develop software that will run on Windows (and that will forever be handcuffed to Windows). I do not wish to develop such an abomination, but many people won't have the same moral objections. VS is Microsoft's "Office for developers" application. It's only reasonable to tout the features os languages and compilers not available elsewhere from Microsoft as features of the whole thing, because Windows developers have no other option.
- citizenparker 17y agoVS is required to develop software that will run on Windows I'm sure the user base of the delightful open source #develop making Windows apps will be sad to hear this, as will everyone using VS to develop against Mono. Which compilers are part of VS that aren't available elsewhere?
- rbanffy 17y agoMono is something weird. I confess I fail to understand what drives clever people to hand over the design goals of their open-source project to Microsoft. They are clever people doing an extraordinarily stupid thing. And .NET apps are as much Windows apps as Java or Squeak apps are - they happen to run on Windows and, if you care enough, you may be able to run them elsewhere - and many do. At least until the next broad Microsoft patent-infringment lawsuit. Mono is toxic in that regard - Microsoft may decide to start a FUD campaign anytime they want and Mono just gives them a huge stick. If that's not a dumb thing to do, I am not sure what would qualify. As for the compilers, I am quite sure you cannot obtain any Microsoft compiler that is sold as part of VS without at least some part of VS. You can run them from the command line (if you could call cmd.exe a command-line) and you can download them from Microsoft for free, but saying that they are available "elsewhere" is a bit of an overstatement.
- trezor 17y agoYou obviously have no idea what you are talking about and if anyone is doing FUD, it would be you. The .NET compilers costs absolutely nothing and are part of the free (as in beer) .NET SDKs you can download whenever you feel like. As for mono: Microsoft has actively supported the community, helped out with getting moonlight (the opensource Silverlight implementation) working, and as part of the Silverlight package you have IronPython, IronRuby and the DLR (dynamic language runtime) which are all largely opensource. Even if Microsoft wanted to bail out at this point, it would be too late. Not to sound rude, but I think you had one thing right in your comment: "Mono is something weird. I confess I fail to understand". How about the simple explanation? The .NET framework (despite the silly name) is a solid framework, C# is a good language, the CLR is sexy and people want to use it on more platforms than just Windows?