VS 2010 - what are the shiny parts?
-
without it, you're not a true MS fan.
"it"? You mean the sarcasm?
-
I like stuff that's new and shiny just like any other geek (after all, I just upgraded to Windows 7 which is nothing but shiny). However, I've also spent a lot of money on MS upgrades over the years that really brought little new to the party. And so, I ask the more experienced among you:
- What makes purchasing VS 2010 worthwhile?
- Can I do things with it that I can't do in VS 2008?
- Does it come in a hyper intelligent shade of the color blue?
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting ServicesI am liking VS2010 for the better IntelliSense (especially with javascript/jquery), the tooling refresh (particularly ASP.NET MVC and the Silverlight/WPF experience), multi-targeting, the better deploy/publish paradigm for web-based projects. I use multi-monitor support daily. I like the debug experience a lot better. If you haven't tried watch-variable pinning yet you'll certainly enjoy that. Pex looks like the solution to the 70% of code that we can't find budget for to write tests. The WPF-based code-editor is great for moving around in the code file. Block-shaped editing is awesome. When editing, you also get better visibility and highlighting of tokens/classes/params/etc (when your caret is in one, it lights up all other instances in the class file). Those are some...I've been using it for quite some time so it's hard to remember what isn't there in 2008. As for comments around 'upgrading all the time'...two times in five years isn't by any means 'all the time'. I would suggest that anyone not using the tools available from one version to the next is either maintaining legacy code or stuck in their ways and not willing to spend the time to learn new, valuable career skills. Cheers, -jc
-
The WPF and Silverlight designers are much better - but I rather like typing xaml so I am not sure how much use I will get from them.
If you prefer editing the XAML you'll really enjoy the better editing story with IntelliSense improvements. Cheers, -jc
-
If you prefer editing the XAML you'll really enjoy the better editing story with IntelliSense improvements. Cheers, -jc
I hope so - the intellisense in the VS2008 XAML editor often freezes - typing in "
-
Try it and see for yourself. With 3rd party add-ins, you'll end up running into OoME. I believe some of the 3rd party add-ins even have workarounds for this. When it's baked in, there's no overhead for the add-in. Less bloat. And I don't have to buy a 3rd party add-in to boot.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Judah Himango wrote:
When it's baked in, there's no overhead for the add-in. Less bloat.
Boy, talk about subtle sarcasm. ;)
Gary
Nope. Try it yourself: VS without Resharper and with. See what kind of performance and memory usage you get.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Nope. Try it yourself: VS without Resharper and with. See what kind of performance and memory usage you get.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
I find it a little ironic (and possibly amusing) that the first component on it's list to download/install is the "Microsoft Application Error Reporting" component, whatever that is. :)
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Blow
-
If I wanted longer coffee breaks, I would have stayed with C++. :)
Christopher Duncan
www.PracticalUSA.com
Author of The Career Programmer and Unite the Tribes
Copywriting Services -
The sarcasim was ANY Microsoft software without Overhead. I don't think it exists - anywhere. It is always bloated. :) And slow....
Gary
Yeah, but I didn't say "zero overhead". Nobody writes software with zero overhead. Instead, I said, "less overhead than loading a large 3rd party add-in".
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Yeah, but I didn't say "zero overhead". Nobody writes software with zero overhead. Instead, I said, "less overhead than loading a large 3rd party add-in".
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
Yes, but the "large 3rd party add-in" would be smaller and faster than the MS built-in feature. It's all relative.
Gary
No, it isn't. Try using Resharpher on a large solution. Now try with VS2010. See it for yourself.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah Himango -
No, it isn't. Try using Resharpher on a large solution. Now try with VS2010. See it for yourself.
Religiously blogging on the intarwebs since the early 21st century: Kineti L'Tziyon
Judah HimangoJudah Himango wrote:
No, it isn't. Try using Resharpher on a large solution. Now try with VS2010. See it for yourself.
Judah Himango wrote:
Try it and see for yourself. With 3rd party add-ins, you'll end up running into OoME. I believe some of the 3rd party add-ins even have workarounds for this. When it's baked in, there's no overhead for the add-in. Less bloat. And I don't have to buy a 3rd party add-in to boot.
Okay Judah, I'll give you one bad add-in for one bloated application is possibly worse than MS build-in code. You made a generic statement about 3rd party apps, which is still wrong. But, from the resharper site: How ReSharper Helps Visual Studio Users Continuous code quality analysis in C#, XAML, XML, ASP.NET, and ASP.NET MVC. I don't program in those apps, so I have no need for resharper, I guess. Over and out.
Gary