is there any major performance changes in 2010.
There were a lot of complaints about perf during the beta cycle. They even delayed the RTM release date by a few weeks to buy extra time to work on it. It sure looked like cloudy with a chance of meat balls to me, but I've got the Ultimate edition running on two machines that also have VS2008 and they both are very responsive. Many of the awkward delays in VS2008 are gone. It is all around snappy. Only starting the debugger seems a bit slower.
They did a great job, it is a fine product. You won't be disappointed. Defrag your hard drive before you install it.
Related
Is Visual studio 2010 slower than 2005? I just had my laptop upgraded to windows 7 64bit with visual studio 2010, and vs 2010 is much slower than vs2005 was when I had xp. Any upgrades or configurations you can think of that might help me out?
Turn off the "Enable rich client visual experience" and turn on "Use graphics hardware acceleration if available"
Extra features always come at a cost. If you don't upgrade your computer at a similar rate you upgrade your software, you'll find it gets slower and slower.
About VS2010 specifically, the UI uses WPF, so you need at least a decently passable graphics card to handle it. Intellisense also got a lot better, so it will use slightly more CPU.
For what it's worth, 2010 runs very smoothly on my computer.
Depending on your setup, Visual Studio 2010 can be faster than VS 2010 or slower. I'm not sure from your question in what way Visual Studio is running slower, though.
Is it just Visual Studio, or is anything else slower?
You mentioned you're running Windows 7 x64. If you have more than 4 GB of RAM, this is a good idea. If you have less than 4 GB, you're probably going to be slower than if you're running 32-bit. It's also worth looking at your Windows 7 performance rating--if it's low, applications like Visual Studio will be slow too.
The hardware requirements are listed over at http://www.microsoft.com/visualstudio/en-us/products/2010-editions/ultimate/system-requirements, but those are bare-bones requirements. If you're doing SharePoint development, then you'll need a much beefier system (SharePoint will compete for a lot of your system resources). I'd want at least 1 GB more RAM than recommended there even without SharePoint. The processor speed is fine for multiple cores, but if you have an old laptop 1.6 GHz and a single core won't be that fast.
Most people find an SSD drive helps incredibly.
Launching Visual Studio does seem to take longer, but to me it runs faster once it's up. F1 help is non-blocking now. Compiles can be done in parallel. Navigation and adding references is faster.
Grab the productivity power pack from vscodegallery.com--that adds a lot of shortcuts.
Visual Studio has more features than previous versions. Most people install everything. It may be better to just install the features you need.
The previous poster mentioned having a good video card or chipset. That's probably a good idea, but disk I/O and CPU are probably more important.
We've recently upgraded to the final release of VS2010 and are experiencing very slow build times compared to the same code under 2008. I was wondering if anyone else is experiencing the same so I can work out whether it's just our environment or not? A few details:
Using VS2010 Ultimate on Windows 7 with fairly beefy machines, talking to TFS 2010.
The solution has been upgraded from VS2008 but still builds against .NET 3.5 and ASP.NET MVC 1.0.
It doesn't seem to be the compilation itself taking long but something else in the build process. This is because even projects that are up to date and don't need compiling are taking a few seconds or so to process.
It's not due to an Visual Studio addin because a couple guys in the team haven't installed any.
The first build after loading VS2010 is pretty quick, then they seem to slow down over time. For example on of the projects in my solution just took 00:00:00.08 to process after a restart. (The project was up to date and didn't need compiling) I then immediately hit rebuild and it jumps to 00:00:01.33.
We're also experiencing the problem with another solution that uses .NET 4.0 that was building perfectly fine under VS2010 RC.
There are no build events or anything like that I can blame, just straightforward assembly builds.
The IDE is not very responsive during the slow builds.
Anyone else has similar problems?
Update: It looks like the resolving assembly references is taking a long time. Looking at the MSBuild diagnostic output or the example above the first build has 30ms for ResolveAssemblyReferences, the second build has 800ms. Subsequent builds seem to be taking longer copying stuff around, e.g. CopyFilesToOutputDirectory jumps from 1ms to 27ms.
Found the problem; turns out it was a rogue build task causing the problem. In my MVC website project I was using the YUI Compressor task from http://yuicompressor.codeplex.com/ to compress my script files and copy them over to my JavaScript unit test project. Everything was fine until this ran, but as soon as it ran it slowed down builds of all other projects! Even rebuilding single projects in the solution and going nowhere near the MVC website were slow. Must be a leak in the task or something like that...
I'm also experiencing extremely slow responses generally from VS2010. I can type in a phrase, sit back and watch it typed out onto the screen a couple of seconds later. Using it's internal web server is extremely slow even when not debugging. It's unusable.
Running it on Win7 Professional x32, with a web project built on .NET 4.0, converted from .NET 3.5 on VS2008 which ran fine but was when I was using W2k3 as my development machine to keep the speed up.
All these are run as virtual machines using the latest version of VirtualBox (currently V3.2.8 r64453) on Linux Ubuntu 10.4 x64 on a massive machine. 2 x Intel i7 2.8GHz (8 virtual cores), 12GB RAM, NVidia 9600 GPU with 512MB RAM.
VM is set up to give 2 cores to Win7 and 4GB RAM and 96MB Video RAM. VT-x, 2D & 3D Acceleration and Nested Pages are enabled.
VS2010 has been tried with and without Hardware Acceleration (as it uses WPF to display it's text editor! [why???]). With, you lose the text editor and menu bars; without, you get a barely usable system. I also have Reflection and Visual SVN installed. The machine is used for nothing else. Anti-Virus is run manually to keep the load down!
[Rant Warning:]
VS2010 runs like a dog and if it wasn't for the fact I've spent 11 months on this project for a client I've been working for for 7 years, I'd be redeveloping in PHP on responsive tools. I left M$ OS's for my business OS 2 years ago precisely because of freezes, slow downs and inexplicable changes taking weeks out of my productivity. Cost wasn't the issue, it was service.
[Rant Over]
I'm aware there are 3 items to this, VirtualBox, Win7 & VS2010. It may be best for me to set up a Win2008 server VM and install VS2010 on that, I don't know at this point.
If anyone has any clues how to get VS2010 to respond in a timely fashion I'd love to hear them.
Craig
I had some extremely slow build times on a solution that included an MSUnit project (with only about 5 tests in it). The tests were not set to run on each build or anything like that. When I unloaded the project, the build became much quicker.
Just for anyone's sake. I had slow compilation times because of an extension, disabled extensions and 10 x more speedier (probably a bug in one :s)
I had the same problem one week ago. Reinstalling .NET 4 framework helped me.
Had the same issue, solved it by changing my default browser from IE to Chrome.
I'm about to start a new WPF project and there are a number of things in 4.0 that I need (multitouch for one). I've heard that VS 2010 beta 2 will be released at PDC in November so I'm considering starting the project in beta 1 now, then migrating to beta 2 when it becomes available. Assuming I only need to live with the environment for about 3 months would it be reasonable to start this project in VS 2010 beta 1 or is it not ready for daily development?
I'm not sure you're going to get the answer you're looking for here. In part because it's really hard to understand what you mean by "ready".
Visual Studio 2010 Beta1 is a beta product and hence will have beta issues. It will crash more often, have more performance issues, less features and generally speaking not as smooth of an experience as an RTM product would. That's essentially the definition of a beta.
But is it ready? I use it on a daily basis at home and work for essentially every project I work on (including those which ship on the 2.0 or 3.5 framework). Yeah I occasionally run into some annoying bugs. But nothing so severe that I stopped using the product.
I've been doing a few things myself with .NET 4.0 recently, nothing major or for production, but it seems stable enough.
Though others may have had a different experience to me.
As it's beta software, I wouldn't recommend using it for Production purposes until it's fully released, or at the point of RC.
However, like I say, it seems to be stable enough in the .NET aspect of things, but I've not tpyed with WPF 4 yet so I would leave that decision up to you.
Thinking about installing Visual Studio on my Asus eee 1000HE. Since it is not a very powerful machine, I am wondering if I should install 2008 or the new 2010. Looks like there has been a lot of changes done to the UI, etc. Does that mean that it now runs smoother as well? Or is it actually heavier to run?
Considering that VS2010 is currently only available as a CTP release, I'd install VS2008.
Once VS2010 is fully released, without debug information and with optimizations enabled, ask this question and consider using it. For the moment, if you have 2008, use it. I doubt 2010 will be faster on your 'slow' hardware.
2010 is much slower on older machines in my opinion. I am running it currently on a Dell 700m with 512MB of RAM and while it does run, it feels sluggish and significantly slower than Visual Studio 2008. (Remember that it is a beta though, I am sure that performance tweaks are forthcoming)
It is a little bit more difficult to judge the performance differences since you are running it in a virtual machine at this time (no stand alone beta out yet).
Edit: If I am incorrect on the inability to run it outside of a virtual machine I apologize and stand corrected.
Does that mean that it now runs smoother as well? Or is it actually heavier to run?
This is an old post, I know, but I just had to chime in and laugh: lol
I had a pretty decent overclocked Wolfdale-based machine I built for gaming. Fast enough for virtually everything I need to do on a computer, except for editing text files in Visual Studio 2010. Just scrolling up and down in a C# file maxed out one of my cores. No joke.
So I upgraded to the new Sandy Bridge 32nm CPUs (3.3GHz, unlocked model) in an enthusiast motherboard, with 8GB of Corsair RAM, and scrolling moving the cursor around in a text buffer in VS2010 is using 30% of the CPU (that's right, it's using multiple cores). This is with no plugins and outlining turned off.
Vim in the same file, doing pretty much anything I can think of, shows 0% CPU usage, always.
VS2010's editor performance is absolutely shameful. There's no other word for it.
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.