VS2010 vs VS2008 SP1 on Windows 7 - visual-studio

How stable is Visual Studio 2010 compared with VS2008 SP1 on Windows 7?

So far, VS2010 is only available as an early CTP (from last November) in a VPC, so it's not really a relevant comparison. It's for looking at, not using.

I cannot speak for VS2010 on Windows 7, but I have been using VS2008sp1 on Windows 7 as my primary development machine and it works great.

Considering I've never gotten VS2008 to crash on ANY OS, id say its hard to get any better than that. Granted I may not have put it through its full paces, but I have hit a wide range of abilities over the past year or so since moving to VS2008
EDIT:
Nevermind I just remembered crashing it when a former coworker insisted on using Source Safe, which ran off a laggy server, the lag alone brought VS2008 down.

Related

Visual Studio 2010 - Very slow display update on MacPro running Win7/Bootcamp

I'm a .Net developer running Windows 7 Ultimate (x64) on a 2010 MacPro (2.27Ghz/6GB RAM) using Bootcamp. Until about a month ago its been, imo, the ultimate dev workstation. However recently I've noticed that Visual Studio 2010 takes a very long time to redraw its windows. This is most noticeable when switching to it after its been in the foreground.
I don't get this problem with other Windows apps and am baffled because the machine has more than enough grunt to handle a few MDI'd windows yet grinds for up to five minutes sometimes when reactivating the VS environment - the screen update seems to slow everything down. My colleagues are using identical hardware and software but running Windows under Parallels on their Macs does not lead to this behaviour.
I'm getting desperate (and I've asked this same question at apple.stackexchange.com) - does anyone know why this might be happening and whether there's a fix ...?
Improving Performance by Changing the Visual Experience
You might have a problem with Hardware Acceleration in VS2010. I had an issue with rendering applications built using WPF because of this.
Give it a try:
http://blogs.msdn.com/b/zainnab/archive/2010/06/22/improving-performance-by-changing-the-visual-experience-vstipenv0017.aspx
And if that doesn't fix your issue, go to your video card settings (nvidia or amd) and do a "reset settings". Then try again.

What's the stability of VS2010 like?

I'm talking about VS 2010 Professional/Ultimate RTM (not express versions).
Google doesn't show much other than stuff about the beta 2 and RC versions.
Will it run OK on a Core 2 Duo E6550 2.33GHz with 3GB RAM and NVIDIA GeForce 8400 GS?
Edit:
How does it go with R# 5.0?
I've been using the Premium RTM daily since release and experienced no problems whatsoever developing with C#/ASP.NET MVC2.
My machine is also similar specs to yours and has been running just fine.
Regarding your edit, I've also been doing all of this with Resharper 5.0 - again, no problems whatsoever.
I haved runed it for since release now, and i must say i have had no problem at all, but hey diden't have any with VS 2008 ether. But evythings works great fast and all this while looking nice :D Eclipse go home .D
I installed VS 2010 Ultimate RTM, in my laptop and its specs is exactly like yours except the Nvidia, and it is working perfectly with no problems.
I've been very impressed with 2010.
Even the Beta and RC releases were stable. I find VS2008 SP1 hanging on average twice a day for me.
So far the only thing to crash 2010 was a third party plugin.
Stability: Good
SVN Support (using ankh): Good
2008 to 2010 project upgrade: Good.
No reason not to upgrade.
The only thing is that it requires 3 restarts on XP and 1 on 7...
I was running the RC for a few months before the RTM version was released, and even the RC version was rock solid as far as I was using it.
I didn't use a stopwatch but I got the impression that it is a bit slower at startup than its predecessor.

Install Visual Studio 2010 Beta 2 beside VS2008

I am too paranoid to install VS2010 Beta 2 on my production machine beside VS2008 without hearing from people who have already took the plunge. I know MS says it's OK, but that does not necessarily mean it will work.
Has anyone successfully installed VS2010 Beta 2 (preferably Ultimate edition) on their production machine with no negative consequences?
If you're that paranoid (and perhaps reasonably so!), have you thought of running it up in a virtual machine ? You can then point it to the same source repository, and be confident that the two won't interfere.
I have installed VS2010 beta 2 in my machine, together with VS2008, and it seems to work fine. There were two compelling reasons for me to start using it right now, both related to Silverlight: unit testing and visual designer.
Take a look at some of the list of known issues in VS 2010 beta 2.
I have installed it to a machine with VS 2008 on it that I don't care about. :)
Looking at the "correct" uninstall procedure from that link above makes me think that not putting it on a production box is a good idea... Going from that beta to the next one is going to be a PITA.
And whoever said they are WPF/Winform it won't conflict is crazy. .Net 4 installs side by side, yes. But there are policy files and binding redirects installed for all editions on your box because VS 2010 can also build / debug / test .Net 2/3/3.5 assemblies. You are touching every .Net runtime on your box when you install VS 2010 (like it or not).
It's working for me; I haven't seen any problems so far (admittedly in, like, one day).
That said, I'd be a lot more cautious if we didn't have a separate build server for our production builds.
Since it's in Beta, I would not install it on a production box; not even in your daily development machine. The best solution is a virtual machine, which is the way I always try beta software.
VS2010 beta 1 worked perfectly alongside VS2005 and VS2008 on two PCs for me. (One XP, one Vista)
It also uninstalled cleanly in both cases.
This is no guarantee of Beta2 working perfectly of course, but you should be ok. Generally the advice is: don't install Beta visual studio releases on development machines - use a virtual PC or a PC you don't mind reinstalling the OS on.
I have a parallel install of VS 2008 and VS 2010 beta 2. The only negative consequence is that some Microsoft DLLS (Microsoft.Test...) that is part of the unittest framework on both vs2008 and vs2010 needs to be referenced by version in the vs.net 2008 projects. Otherwise vs2008 may just pick the vs2010 reference by default and you get compilation errors.

Has anyone ran into any issues developing on Windows 7?

I want to trial Windows 7 but wondered if anyone who has done so already ran into any issues specifically related to development?
i.e. problems with VS2008, SQL Management Studio and SQL Server, MySQL, PHP etc. etc.
Examples from XP -> Vista: in Vista there was a sudden loss of an SMTP server. And there were initially (if I remember correctly) issues with VS2005 with I seem to remember a patch coming out later to remedy.
EDIT: or on the contrary any big advantages or benefits to developing on Windows 7!
I been using windows 7 for a while now.
I been using VS2008, netbeans, tomcat, sql manager studio, mysql etc...
And i actually find it more stable and faster then windows vista.
There aren't many advantages to developing on Windows 7 before it's released. Most development features are a function of the IDE, not the OS. So, you might want to consider instead if you should be developing on Visual Studio 2010 instead of VS2008. Instead, you're more likely to have compatibility issues, although for the most part, Windows 7 is much more compatible with existing software than Vista was when it was in beta.
There could be one advantage to developing for Windows 7 before it's released -- you have a head start in taking advantage of features that competitors haven't yet, giving you an advantage in the market. That's the theory at least. That assumes you're going to develop something that uses a feature only available in Windows 7. That assumes you wouldn't be better off with the larger number of sales you'd get by developing something that works on existing platforms.
The only issue I've encountered so far involves compiling older vanilla C programs with Visual C++. You're usually presented with an error like so:
mt.exe : general error c101008d:
Failed to write the updated manifest
to the resource of file
".\Release\SomeProgram.exe". The
binary is not a valid Windows image.
You have to add an empty resource file to the solution.
More on the issue here.
I've never gotten any of the new audio stack examples working; thus this question. API works, documentation is... a bit lacking at the moment; sure to be fixed by RTM.
Other than that, Windows 7 has been faster than and just as stable as Vista (2 crashes from RTM, 0 crashes after SP1) was for me. Truly, you should be developing on Vista and testing on Windows 7 RC as a general practice with respect to pre-release operating systems; but I think we'll get away with it just fine in this particular case.
My advice would be to not develop on Windows 7. Note that I don't mean you shouldn't target it as a platform, just that you should be doing your development on a stable platform.
I personally won't trust a new release of Windows (or Linux for that matter) until it's been in the wild as a proper product (not release candidate) for many months. For Windows, I tend to wait until the first real service pack plus a month for all the nigglies to be fixed.
For Linux, I'm still using Ubuntu 8.04 LTS, not 8.1, and certainly not the 9 alphas.
Test machines are another matter, you should always have one at the "latest and greatest" level for testing, but I consider the development machine of prime importance, needing a stable platform.
No problems from my end yet, been working on a c# app with visual studio 2008 x64, and php web apps with dreamweaver cs3 and netbeans.
Windows7 seems to be just vista with more bells and wistles and a bit more responsive, not to sure if to much really change "under the hood" so to speak. But I have nothing to back that statement up with...
I've been using Win7 for a couple of months now and never had a problem. I went straight from XP to 7 and the only problems I faced were related to configuring SourceGear Vault to work with IIS7...other than that,it's been all good.
I use VS 2005, VS 2008, SQL Server 2005, Infragistics NetAdvantage, and a couple of third party components.
Although I haven't seen any advantages for the development side of the applications, I'd recommend you to upgrade to Win7 only for the better feel of a complete OS. I mean XP was good, but I really dig Win7.

Does anybody have experience with Visual Studio 2008 on Windows 7?

Has anyone already tried this, anything particulair that I need to be aware of?
Yep, been running it for a while and I haven't hit any problems yet. Can't say I've use it all day every day, but I've built WPF, WinForms, Web and Console apps with it for testing various things and haven't had any hitches.
I have it on my Dell X1, which is effectively my "NetBook", and it's really pretty rapid. The only glitch I have had at all is some problems with graphics acceleration, but that's down to the Intel driver I'm using being an old XP driver, and it was easily worked around.
I've been running it inside a VM in Parallels Desktop 4 on a MacBook Pro. Absolutely no problems to speak of.
(There's no sound in Windows 7 as virtualized through Parallels, which is a known issue — but not very pertinent to the operation of Visual Studio.)
Jeroen,
I've been unable to install the 2008 Team Developer edition - keep getting a permission error. I was, however, able to insall the 2008 Team Database edition. I normally install both editions, so am kind of bummed about not getting the Developer edition to install. Screenshot of the error is here if you're curious.
No Problem with team edition, but only using it for web projects.
I've been using it at work since RC1 and have not run into any issues. Have developed a WinForms app, a WebForms site and now working on a MVC project.
I have had zero problems running Visual Studio 2008 Pro on 32 bit and 64 bit editions of Windows 7 for full-time C++ development.
If the application you are developing doesn't behave correctly under UAC you may will need to run the IDE as admin otherwise it won't run correctly under debug (this is the applications problem, not Windows 7 or Visual Studios).
Others seem to have problems with access rights/permissions, this should also be fixable by running the IDE as admin (via right click) or more permanently via the compatibility tab in the shortcut properties.
I don't know why this happens, is probably related to their particular user account settings.

Resources