VS 2008, or VS2010
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I have to say I prefer 2010. I've used 2005,2008 and now 2010. Some of the features I like in particular are The TDD support ( Big big plus point.. but could be better when generating classes) Can move code windows around. Snap them in and out of the IDE Support for .net 4.0 I find the interface cleaner and easier to use Conditional Breakpoints one thing I do miss is the support for SSRS so I still have to use 2008 sometimes I've also started to use extension more in 2010 .. and they make life easier as well Eg Power commands, Productivity Power Tools, VS10x code Map and method block VS Commands and integration with SVN Source control
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I'm using both VS 2008 and VS 2010 for different projects so I can compare the differences and I have to say that I have not experienced the problems some folks are reporting here. I do not have add ons except for tortise svn and ankhsvn so perhaps that is the difference. My machine is a Quad Core Intel with 8 GB ram and I am running VS in Virtual Box machines with windows 7 ultimate for the OS and fully patched (both OS ad VS). As far as why you should choose. That depends on what you are developing. If you are doing WPF or Silverlight development, I would recommend VS2010 simply because the designers are much easier to work with and a great productivity boost. If you are doing Win Forms or ASP.NET development, it really doesn't matter much although there are some things you would find a bit different/easier depending on how set in your ways you are. Beyond that it comes down to cost. If you are not doing WPF/Silverlight and not planning to in the near future it would not be cost effective to upgrade if you already have the 2008 licenses. If you are starting from scratch, definitely go for 2010. After working with both versions side by side since the release of 2010, I really prefer VS 2010 but both versions are capable. I like some of the wizards and templates to get a project up and running quickly though YMMV. <<<>>>> I work in C# and vary rarely VB.NET when forced.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I only briefly tried it once, opening a logfile.txt of about 10mb - vs2010 was unusably-slow, as presumably this was internally converted to a WPF document. (1) is there some "mode" I can set somewhere in vs2010, that will allow opening large text files reasonably quickly ? (2) What's your favorite editor for large text files ? Visual Studio 6 is good enough for me, although it won't load anything beyond roughly 220mb. vs2008 runs out of memory sooner than that, perhaps roughly at 180mb although since like I say I usually use vc6 so I'm not as familiar, but still the text file opens nearly instantly, NOT being converted to WPF of course.
pg--az
-
If you're programming in .NET, I'd go with VS 2010. For C++, I see no reason to go beyond VS 2008 at this point. Hopefully, VS 2010 SP1 will fix some of the more annoying bugs and slow down issues.
Except for a much improved compiler, closer to standard, including some C++ "0x" features.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
if you do WPF stuff and aren't using Blend for the UI, i highly recommend vs2010. Cider (vs08's WPF designer) sucks hardcore. If you're using TFS as your source control/bug tracking, then i'd recommend you match versions. right now we are vs2010 w/ TFS '08 and it's nothing but headaches in terms of performance. Other than that, i've not experienced a noticible performance diff between the two in terms of getting aroudn w/ solutions and whatnot. I'm on a Xeon quad (no ht) w/ 4gb RAM, 32-bit editions of everything.
-
Except for a much improved compiler, closer to standard, including some C++ "0x" features.
Rob Grainger wrote:
Except for a much improved compiler, closer to standard, including some C++ "0x" features
That, and the better Intellisense, based on the EDG compiler. Now if it only had a decent code editor...
-
I use VS2010 everyday and refuse to use anything less for any development, period. There have been some great advances and most will save you time and money during development. Sure there is a learning curve and some issues with designers and the IDE, but at the end of the day, it does what needs to be done and more. Switching between versions is just a time waster. If your machine meets Windows 7 requirements, you should be using Visual Studio 2010 now. Any comfort excuses will end along with mainstream support in about two years. Serious developers consider extra RAM, multiple monitors and SSD to be even more productive.
Dwayne J. Baldwin
Dwayne J. Baldwin wrote:
Serious developers consider ... multiple monitors ... to be even more productive
Grabbing popcorns and waiting for John C to see this...
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I ran VS 2008 for about 18 months before I just couldn't handle it anymore. Over the course of that year 2008 got worse and worse; crashing, terrible memory leak, most importantly it just kept getting slower and slower and slower. It became so unbearable I wound up switching to notepad ++ to do most of my heavy lifting and coding for longer documents. I had the ability to switch about 3 months ago but decided to stick with 2008 for a few reasons, mostly just because I didn't want to have to re-do all my settings and set up tortoise svn again. Plus I had Dreamweaver cs5 and I had become quite fond of it. 2010 is so much better though. I swear the intellitype and autocomplete is better. Dreamweaver CS5 was great but I like VS 2010's layout and preference set up better. I also love being lazy and using the format option to clean up my messy code. I hope this helps.
-
I only briefly tried it once, opening a logfile.txt of about 10mb - vs2010 was unusably-slow, as presumably this was internally converted to a WPF document. (1) is there some "mode" I can set somewhere in vs2010, that will allow opening large text files reasonably quickly ? (2) What's your favorite editor for large text files ? Visual Studio 6 is good enough for me, although it won't load anything beyond roughly 220mb. vs2008 runs out of memory sooner than that, perhaps roughly at 180mb although since like I say I usually use vc6 so I'm not as familiar, but still the text file opens nearly instantly, NOT being converted to WPF of course.
pg--az
The best editor for large text files is hands down Notepad++ It has a multitude of options and plugins that ship with it and even more available to download. Most importantly it's freaking fast, and can handle everything I've thrown at it so far. I just opened a 25mb raw (.nef) file in less than half a second
-
I'd hate using sh*t like that, it would be like going back to VS.net or 2003.
Hans Dietrich wrote:
Microsoft PM who said that VS2010 would be "the new VS6" is an idiot.
He was also re-assigned before it shipped. I think he tried to change the culture of the department from the top down and failed to make any serious improvements. Their performance test coverage was also pretty heinous, so they missed a lot of common cases, patching like crazy at the end. I am hopeful that they will stick with the 3-4 release strategy to make VS into a good product. From what I read this was supposed to be the big destabilizing release where they cleared out a lot of cruft, and then they were going to start building up from here. It looked like the tools team was the long pole and they shipped whenever the framework was done.
Curvature of the Mind now with 3D
That reminds me of the Mac commercial, where the PC asks Windows of the Future (a century ahead) when Microsoft would fix the problems of Windows freezing up. Windows of the future then immediately freezes up! So funny because it's true! I remember it whenever Windows takes 45 seconds to delete a 1K text file.
-
Wow. I've never heard anyone say VS2010 was faster doing anything.
Best wishes, Hans
Add me to the list of people who think it's faster. We have a 400k lines of code winforms project with Developers Express controls, CodeRush/Refactor Pro installed, and various extensions. Works pretty good for us. We use C#, not VB, if that makes a difference. We all used the beta of 2010 just to get off 2008 because that was a nightmare for us. We would have to restart studio 5 - 6 times a day. Now we don't have to at all. I also maintain a 10k+ lines of code ASP.Net web forms application that works well to. Although, I will say I never use designers for that. It's also in C# and I can leave it open for weeks without restarting. I also use DX controls, CR/RF Pro, and various extensions.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
Interesting question and discussion, but no one has mentioned the relative speeds of executables generated by the two versions. In particular, has anyone noticed a speed difference for C++ programs over VS 2008 and VS 2010?
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
-
Interesting question and discussion, but no one has mentioned the relative speeds of executables generated by the two versions. In particular, has anyone noticed a speed difference for C++ programs over VS 2008 and VS 2010?
Alan Balkany wrote:
has anyone noticed a speed difference for C++ programs over VS 2008 and VS 2010?
If you use the C++ Standard Library, move semantics introduced in the VS2010 compiler definitelly make a difference.
-
Alan Balkany wrote:
has anyone noticed a speed difference for C++ programs over VS 2008 and VS 2010?
If you use the C++ Standard Library, move semantics introduced in the VS2010 compiler definitelly make a difference.
Thanks. Do you know which is faster for non-STL C++ ?
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I wish 2010 had a report project template for SSRS. Other than that I like it better than 2008. Just be sure to get the find and replace dialog patch if you go with 2010. If not, every time you open the dialog to find or replace (ctrl f or ctrl h), it's window will resize. Totally annoying....lol
-
Thanks. Do you know which is faster for non-STL C++ ?
Alan Balkany wrote:
Do you know which is faster for non-STL C++ ?
I don't really have any data, but can't see a reason why would VS2008 produce faster code.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
I prefer VS2010, but I seem to have had a better experience than others here. I agree with other posters who say try the express edition of 2010 first. Maybe this will help. Single core, less than 2GB RAM: 2008 Dual core, 2+GB RAM: 2010 If you're doing WPF development, you might be sold on the improved stability of 2010 anyway. Once upon a time I used to have a lot of crashes, particularly while doing things with WPF, and I dug in to find out why. It was my antivirus interacting poorly with WPF components. A few updates from the vendor happened and it's no longer been an issue. YMMV, I suppose.
-
OriginalGriff wrote:
Why? If we use your argument, we will then standardize on the next release, and then the next...
The point is that you have two to choose from, not having moved to 2008 when it became available. That being the case, the newest available makes more sense from a long term support point of view. When/if VS2012 comes out, You could have three choices if you haven't standardized yet, the support issue becomes more significant, since it impacts when you have to spend money on replacement software. If on the other hand, you have already standardized, then it becomes a choice driven by what benefit the next release might bring. There is also the issue of upgrading your applications to accomodate changes in the toolset (C++ VS2008 from VC6 was pretty painful, VS2010 from 2008, not so much). Just keeping up with the next release could be more work than it's worth; eventually you'll have to bite the bullet and move along, but there are advantages to putting it off until you have no choice, even at the cost of more work at that time.
OriginalGriff wrote:
it does seem sluggish compared to 2008
It is slower to start up, for sure, but it seems to be doing more validation during startup than 2008 did. It is also a bit slow displaying XAML in the designers compared to vs2008, but not enough so to be a problem. As far as the text editor goes, I guess I just don't type fast enough to notice any problem...
"People who bite the hand that feeds them usually lick the boot that kicks them." Eric Hoffer
Rob Graham wrote:
Just keeping up with the next release could be more work than it's worth; eventually you'll have to bite the bullet and move along, but there are advantages to putting it off until you have no choice, even at the cost of more work at that time.
You have to be careful how far you take that. It's like quicksand. You could wind up with different responsibilities by then and be totally helpless to update it. I used to work for a company about three years ago that took old VB5 apps that other companies no longer had time to maintain, and migrated them to current technologies, and I'm running into things like that today at my current employer. (Got out of the consulting business though!!) So, don't put off the update forever, because you might not ever get around to it.