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
Well it's rather simple - I use both (as I doing some WindowsCE development and you get no VS2010 love for it). But overall I love working in VS2010 - it just feels better and with all the goodies (NuGet, Productivity Power Tools, ...) and of course TFS (used to be MSDN pro/VS pro subscriber - now switched to premium) it a no brainer what version to use on a day to day basis. I've got no issues at all (but I have a "decent" machine - 4cores@2.5GHz, 12GB RAM that helps "a lot"). I get some slowdown from time to time - but I'm rather sure that this is Rsharper-related because I've got the same issues on VS2008. Only thing that really killed the fun so far was a bug with the Async-CTP that killed the data-visualization during debuging (only in C#) and that could only be solved by installing the SP1-beta. So my recommendation would be: MSDN! - so you get BOTH and can choose at will.
-
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
2010 rocks so hard and with SP1 on the way it's a definite winner. Plugin support is unparalleled to 2008. Once you go 2010, you won't go back.
-
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
Still using 2005 Standard ourselves. I/We can't see shelling out for a "better" newer version considering it handles everything we throw at it so far. Migration for all the people that work with/for me would be a pain (even if just for the Admin of uninstalling/reinstalling/dependencies etc...) We have 397 products/projects (some in idea/snipit stage, all the way to finished code) (had to look in the code base server for that info...whew there's a lot of junk :P) and all of them fit nicely in 2005 so I really cant give you any reason to upgrade. Now on the other hand if your business/programmers are just starting out...Get them the newest thing now. I remember the pain of picking a new dev IDE when the choice was VS6 --> VS2003/VS2005. We went to 2005 because we had outgrown 6 and needed something new and it sucked and was a royal pain. Lots of old software (API viewer comes to mind) had to be replaced for .net stuff and many things that just worked no longer did (sockets....don't even get me started on .net sockets!). The question was not to upgrade or not, it was upgrade to what, so we went with the newest thing on the market at the time hence VS2005.
-
Wow. I've never heard anyone say VS2010 was faster doing anything.
Best wishes, Hans
-
What sort of work do you do ? I wonder if it's faster for people who do no GUI work, for example, b/c I find the designers freeze a lot.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Any recent integrated Intel chip is normally enough. I've used it without GPU as well (we do a lot of remote desktop on the server) and yes, I feel the difference, but it's not really bad. I've used VS2010 a lot, and I find it slightly faster. I also love the new features (I do multi screen occasionally, for example).
-
Funny, ASP.NET is precisely what I tried to do ( a small, simple site, and I never use the designers, but I found it sometimes insists on loading them all the same ) and I gave up after a day as I found it was unusable. I have no add ins installed, and I am using a quad core machine with 20 GB RAM.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
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 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
-
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 have anything at all to do with C++/CLI, avoid VS 2010 - even 'plain' C++ with the /clr switch on for some interop in the project turns the source editor into little more than notepad with syntax highlighting. VS 2008 was much better for our use case - lots of existing (and still valuable) C++ with a .net front end. Unfortunately, we have had to migrate to 2010 as we needed some functionality in .net 4, but source browsing, intellisense and F1 help are just painful. See: https://connect.microsoft.com/VisualStudio/feedback/details/501921/c-cli-intellisense[^]
-
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
Anything but VS2010. Just about works for c#. But for C++ is so unstable that someone ought to be suing Microsoft. Just wonder what the engineers at Microsoft do for a living - if we produced software of the quality of VS2010 we would be fired - even using their own Wizard to create Hello World in C++ (native) the IDE crashes - pathetic. Stick with VS2008!
-
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.