Developers React to Visual Studio 2010 SP1 (Updated)

Visual Studio 2010 Service Pack 1 (SP1) was made available for download by MSDN subscribers on Tuesday March 8 and for public download on Thursday March 10. With shipping versions of VS2010 SP1 finally in the hands of developers, early reaction to the service pack is starting to roll in. No surprise, with an update as large and involved as this service pack, the compatibility picture can get complex.

Sean Hederman, a developer from South Africa, responded to an earlier Desmond File blog item on the VS2010 SP1 release. He wrote: "SP1 breaks a whole bunch of stuff. MS clearly didn't bother testing it or something. [I'm] rolling back the SP1; they might have to scramble to fix this one."

Dave Crozier wrote that Visual Studio 2010 under SP1 "now runs slower than before" and produces memory errors. He also complained about the loss of SQL IntelliSense support. A C++ developer out of England, who identified himself as Stephen, said SP1 failed to address numerous problems his team has faced when working on unmanaged code projects with earlier versions of Visual Studio. His team, he said, had hoped to move off of Visual Studio 2005.

Others were more positive. One developer raved about the "vastly improved help client." Another developer calling himself Brad said the SP1 "launches quickly, works great and has tons of valuable features." He wrote that his team has experienced "out of memory" errors that force occasional restarts, but described it as "a minor annoyance."

Compatibility Picture
The comments area of Jason Zander's blog post announcing the VS2010 SP1 launch offers a discussion of potential incompatibilities, including with the Visual Studio Async CTP.

A commenter to the post identified as Chris referred to the same IntelliSense problem encountered by Dave Crozier: "Installing VS2010 SP1 will cause you to lose IntelliSense in SQL Server Management Studio 2008 R2 to SQL 2008 R2 databases (and probably R1 databases as well)."

There are known incompatibilities with the SP1 release, including the Visual Studio Async CTP and LightSwitch Beta 1, as well as the Windows SDK 7.1 and Help Viewer Power Tool. On Tuesday, Microsoft addressed one of these incompatibilities when it announced the release of LightSwitch Beta 2. The new beta version is fully compatible with VS2010 SP1, however LightSwitch Beta 2 will not work with the original RTM release of VS2010.

A thread on the Visual Studio Async CTP Forums includes a thread titled I Am Not Installing VS 2010 SP1 W/out Async Support. The thread's creator wrote in his opening post: "Excluding Async as a part of VS 2010 SP1 is a huge mistake and a lost opportunity to bring much needed credibility to the Silverlight developer platform."

It's not surprising that beta- and CTP-grade tooling would not be fully supported in the just-released Visual Studio update. When the Visual Studio 2010 Release Candidate (RC) launched in February 2010, the new IDE version dropped support for the Silverlight 4 beta tooling, which had been supported in VS2010 Beta 2. The Silverlight 4 Tools ultimately launched in May, one month after Visual Studio 2010 shipped in its final form.

In a separate thread, forum moderator Avner Aharoni promises an Async CTP update that will be compatible with VS2010 SP1. "We are now working on providing Async CTP that will run on top of SP1, but it will take us more time to get it ready, we still don't have a final date for it."

There are also questions around the complex interactions between Visual Studio 2010 SP1 and the various Feature Packs, Power Tools and other software.

Brian Harry, product unit manager for Team Foundation at Microsoft offers a bit of guidance in a blog post titled Installing All the New Stuff. He noted that if Visual Studio and TFS are on the same machine, both must either be the release to manufacture (RTM) or the SP1 version. The tools won't work if one is advanced to SP1 and the other remains as the RTM version.

Have you installed VS2010 SP1? We want to hear about your experience. Email me at, or leave a comment below.

About the Author

Michael Desmond is an editor and writer for 1105 Media's Enterprise Computing Group.

comments powered by Disqus

Reader Comments:

Wed, Aug 1, 2012 les DE

made the mistake of accepting the 2010 sp1 update before seeing this forum. Now machine won't even boot. Nice work. Get really tired of wasting upwards of a day anytime there is any change to the machine.

Wed, May 30, 2012

VS 2010 does not work. It crashes all the time...

Wed, May 2, 2012 Le Chaud Lapin Austin, Texas, USA

I wanted to add a second comment which I think is really important: Some of you here are .NET programmers who have used VS2008 successfully to write .NET programmers. You might be astonished to know that the reason you are having so much trouble with VS2010 is...drum roll...because it is written in .NET. Are you surprised? Please do not think I am gloating, because I am not. For years, there has been a kind of war between hard-core C++ programmers and .NET programmers. Many of the .NET programmers insisted that "language as mostly irrelevant", and ".NET is better because it lets me be productive quickly." We hard-core C++ programmers argued that it was not just the language. We argue that, along with a hard-core C++ programmer comes certain fundamental and highly-important knowledge of software engineering, how computers work. You know, things like virtual memory, data structures, performance, mutexes, semaphores, events, WaitForSingleObject, WaitForMultipleObjects, etc. Well, as it turns out, with a system as complex as Visual Studio, which Marcello of Florida pointed out, you NEED people who understand these things. VS2008 was primarily written by such people. VS2010 was not. So, not to rub it in but, for you .NET people, it is a bit of poetic justice. You got what you wanted: proof that a system as complex as Visual Studio could be successfully written in .NET. Apparently not. And finally, there is more bad news. Some of you keep saying, "I hope Microsoft puts out a fix." Guess what? That is simply not going to happen. You see, the people who are able to restructure Visual Studio so that it makes sense are already gone. The .NET programmers ran them out after VS2008. So welcome to the future of Visual Studio. What you see now is indicative of every single version henceforth. Very tragic if you are a loyal Microsoft developers. Your .NET friends actually killed your most important development tool.

Fri, Mar 16, 2012 The Brain, (not Pinky) USA NYC

I have used studio 2005 /2008 /2010. Each one has added more great features and more problems. I recently had a consulting gig to create a new web site. Visual Studio kept locking up on me, took for ever to debug, crashed often. Several times I started to edit a web page and it would hang for over 2 hours trying to open an aspx page. (I went to lunch, then waited some more.) Not sure if it was a result of being connected to Team Foundation Server, or third party vendor control packages. Never had these problems on the home system or last place of work. My boss was frustrated because we had a deadline and Visual Studio kept hanging on me. He ordered me to wipe the hard drive clean and reinstall everything. A week later it started to happen again. In the end the boss thought I did not know what I was doing and let me go, so I am looking for work again. ** It is hard to be professional and create a mission critical application when your tools keep breaking. You would not hire a mechanic to fix you BMW if he shows up with a set of tools from the local dollar store.

Tue, Feb 28, 2012 Rob Ainscough United States

VS 2010 SP1 is the worst development tool out of Microsoft in a long time. VS 2003 held the title for a while, but VS 2010 is a dog of dogs. More of Microsoft's quality assurance (aka testing) going to India coming back with a big check mark as "all good". Pissing off developers trying to push Microsoft technologies is about as stupid as stupid can be ... Ballmer needs to step down and someone who actually understands software development needs to take over.

Mon, Jan 2, 2012 Ken Tait St. Louis Mo

Just discovered that the ATMEL AVRstudio 5 using VS21020 shell has kulled my VS2008 installation!!! Won't enter debug, gives some bs message about corrupt installation. this has toally killed my developement!!! Screw microsoft, time to take them down...

Mon, Nov 21, 2011 Ron

rooshanChina When I use vs2010 sp1 working in the silverlight business application, from XAML file to 'Behind Code' file is to slow, I think there is a bug! could any one see the problem? any help would be very thanksful! I HAVE THE SAME PROBLEM...HELP!!!

Mon, Nov 14, 2011 Shoaib Ali

Totally messed up my env after Windows automatically updated SP1. Every time I start devenv I get Exception details: System.InvalidOperationException: All property accessors must be methods. at System.ComponentModel.Composition.ReflectionModel.LazyMemberInfo.GetAccessors() Opening a project crashes. This is insane!

Wed, Nov 2, 2011 Phil London

This piece of garbage should be removed for download. It's fucked up my pC big time. Yes my PC!!!!!! registry and all. tried registry cleaners as well. A complete waste of 16 bloody hours.

Wed, Oct 26, 2011 dfas asdf

P.S.S. Preserve line breaks when accepting forum responses, dumb asses. Just about any posting worth reading is going to be more than one paragraph. And don't even get me started on the fact that I had to enter bogus data in name/email/location to avoid a "your search returned no results" error page that makes no sense for this form submission. I swear, no one on this planet except me should be allowed to program. Amateurs, all of them.

Wed, Oct 26, 2011 asdf sdaf

VS SP1 is evil. It will fuck up your system beyond repair. Even a restore point won't fix it. Unless you want to reformat and reinstall the OS, do not install VS SP1. I would give my left testicle for someone to write a .NET/C# plugin for Eclipse. Any takers? P.S. Will the assholes who wrote this site please not make cookies a fucking requirement to enter you god-damn captcha phrase. Captchas are annoying enough w/o forcing the user to temporary enable cookies and then disable and delete them. Totally unprofessional.

Thu, Oct 20, 2011 Peter S.

I had no problems installing SP1, but unless Microsoft do something about the terrible editor speed (MFC) this is a dead program for us. Like so many people have already said, they should take a look at how snappy and efficient VS6 used to be. Developpers have less and less time but need more and more time because of the sluggishness of VS2010. I've peeked at VS2011 preview, but had to give up after a few minutes because I discovered that the MFC part just doesn't work. IMO, it's a dissgrace that MS actually sells such slow and buggy software.

Tue, Oct 4, 2011 RN

Have not experienced any significant issues with SP1. Was excited about the new release allowing for nested business objects to once again be used within RDLC's. Have since found that this is possible only if you do not do any Lazy Loading any of the business objects. I have not been able to find a work around for this and as we have a large project that requires Lazy Loaded objects we will have to remain on VS2008 until the reporting in VS2010 can support them.

Fri, Sep 30, 2011 Bernardo Salazar Venezuela

VS 2010 SP1 are killing me slowly. Debugging an app causes VS IDE to hang up several minutes (starting to debug, or stopping), and i dont find a solution. Just i will try to begin develop my aplications in any other language/platform, im very disappointed with MS.

Tue, Sep 6, 2011 Dr.R. Clavan Java

After installing SP1 when starting my application in Debug mode I can wait at least 5 minutes before the (WinForms) application actually appears. Stopping debugging takes another 5 minutes (IDE totally unresponsive). Going to have a look at the new Embarcadero RAD Studio XE2, is 64 bits and makes native Windows applications.

Thu, Aug 25, 2011 Steve Pasadena,CA

We use C++ as our main development. Whenever I type something, the CPU will raise to 40%. I waste half of my day just wait for the CPU to low down. The intellisense is very, very slow.

Sat, Aug 20, 2011 Mac US

I have never seen a Service Pack as miserable as VS2010 SP1. It doesn't install correctly, then it fails to uninstall correctly -- and ruins things so you can't reinstall later. It is literally the worst possible scenario. I recently installed it across four identical VMs and the results weren't even consistent from one machine to the next. Developer products were Microsoft's last undeniable strength. It looks like that empire is crumbling away, too. Welcome to the world of low-bidder offshore contractor software!

Wed, Aug 17, 2011 AJAX

VS2010 SP1 Crashes on find accross project-- WebApp Solution with 2 Projects in it. simple small project with only a few aspx files Also-- copy and past these aspx files causes many build erorrs because of references to controls which are in the copied aspx are not renamed to new id#s like WebForm1 to WebForm2 on the paste-- I am not using master pages

Thu, Jul 28, 2011 Thomas

MS, your installation script is flawed. On various situations it runs in a loop and never finishes. i.e. "Could not create Shortcut Visual Studio Itanium Cross Tools Command Prompt (2010).lnk" The install script doesn't check for such error conditions, and just keeps writing it continuously into the log file. -->Result: Frustrated users!

Sun, Jul 24, 2011 James UK

VS2010 SP1 has totally screwed my development environment... not only does VS2010 not load, nor does VS2008 either - giving Package Load Failures. Have tried uninstalling both and re-installing a number of times, but still no luck. GAC is now listing zero items in it too! Really don't want to wipe the whole machine but thinking that it may be my only option...

Mon, May 30, 2011 Jaz FowCo in front of VS2010 sp1

Wow, sp1 trashed my install and then failed. How can something like that get out of your door Microsoft. I have removed components, change/repaired original install and still failure! Test it! I test my software before I go to production.

Mon, May 30, 2011 João Portugal

I am developing a medium-sized project in SilverLight with services Ria, Entity Framework under standard MVVM. as the project grows FDI becomes increasingly slow. Now is exasperated slow. I am increasingly nervous, as this tool keeps me from doing my job efficiently and therefore I and my team will not meet the deadlines agreed with my boss. This is unacceptable in a microsoft product.

Mon, May 30, 2011 ronmurp

4G RAM DEL Vostro 1710 + Vista SP2 VS 2010 SP1, Plus Refactor and Coderush and GitExtensions Symptoms: 1) SP1 long install time or install hangs: I develop under a Adminsitrator profile, but still had to right-click & Run as Administrator to get SP1 to complete. 2) Out of memory problems: This helped: 3) Odd problems while editing & running, e.g. : - brackets appearing as code is typed (very much like some old VS 2005 problems) - screwing up of Coderush operation - renaming variables unexpectedly - mouseover variable inspection not working - Immediate window: ?myvalue says myvalue is not defined - Slow - with "(Not Responding)" appearing often - VS environment white-out 4) Seen recommendations to switch off hardware acceleration on XP systems. Mine is Vista, but I thought I'd give that a go. Seems to have improved, but hard to judge because problems appear irratically. Largest app causing most problems is 18 project solution (VB & C#) - mixed solutions don't work well. Might try breaking up the solution into several project groups: client, server, business objects; which will still allow debug across project sources, but not as convenient as having one solution for whole app. All current projects are still building for .NET 3.5, so very tempted to get back to VS 2008. Until I move on to .NET 4 I'm not sure VS 2010 is offering anything. But will hang on and keep looking for workarounds for now. Verdict - Not bad for small solutions - 2 or 3 small projects. Overall, not a good experience.

Tue, May 3, 2011 Jerry

Since the brain drain that has plagued MS after Bill’s departure this is just another nail in the coffer. Having been a MS developer since 1993 and having a general attitude of just stay away from SP2 anything MS. I must now say… install any SP at your own risk. We have production websites that are now restarting(more than usual with .net) since SP1… not to mention our DBA is extremely upset that he lost his Intellisence. Our investment in MS technologies has been a heavy one… if this kind of service continues other open source technologies are looking more and more appealing.

Mon, May 2, 2011 Anders Jansson Sweden

After installing SP1, C++ project files could not be opened, IDE crashed!! So now I'm removing SP1 and doing a repair of VS2010.

Wed, Apr 20, 2011 TK

We have a very large app (~1,000,000 lines) and we've started adding WPF/XAML files to it. Now when editing the XAML, devenv grows to around 700 meg and the IDE slows to a crawl. It happens on all the dev boxes here. Win7 & Vista. How can MS not see this problem? I've been programming MS/Windows for 25 years, come on guys, this is horrible.

Thu, Apr 14, 2011 Cody

I also noticed SSMS, in addition to intellisense not working, it runs very slow and crashes frequently. I hope a patch gets pushed out soon.

Wed, Apr 13, 2011 Dean

The SP1 install went well for me; however, I can definitely confirm that Studio runs noticeably slower for me after SP1. I disabled all extensions, and made sure hardware acceleration was on (I have a modern video card). Specs: CPU: Core 2 duo 3.20ghz desktop Windows 7 x64 (without sp1) Visual Studio 2010 Ultimate After using Visual studio since 6.0, I sincerely expect (not hope, but expect) MS to release SP2 to fix this along the many other bugs they left out of SP1. I'll be very upset just to be honest, if MS plows on to without fixing this. I'm getting extremely tired of them taking feedback from customers and using it in the "next" version instead of fixing the current one.

Wed, Apr 13, 2011 Matthew Sheeley Kansas City

Since the update to SP1 my entire development rate has slowed dramatically. I get frequent crashes, freezes and just plain long waits every time it hit the debug button. Unfortunately as I'm connecting to TFS with SP1 I was told I had to be on SP1 as well other wise I would go back. It is actually beginning to become a bit of a joke now...

Thu, Apr 7, 2011 Carter Sacramento CA

Installed with no issues (XP Sp3 32 bit). Existing projects seem to open fine and run fine.

Sat, Apr 2, 2011 Marcello Florida,USA

I don’t think it’s reasonable to expect performance improvements as long as the IDE is based in managed code.

A product compiled in managed code will always be slower that its native code counterpart: Managed code will never have the performance of native code: Therefore, VS2010 will always look slower than VS2008/VS2005.

The managed code + WPF combination is a metaphor incapable - inadequate in expressing in full the complexity of a system such as Visual Studio

Fri, Apr 1, 2011 Fred

The installer has been running for 3 hours now. It has constant CPU and disk activity, so it is not hung. It is writing 7MB/s to mainly 2 files - NTFS volume log, and AppData\Local\Temp\HFI6A81.tmp.html. And my machine is no slouch, it is a Core 2 Quad 2.66GHz, 4GB RAM, running Windows 7. The progress bar has not moved in 2 hours.

Wed, Mar 30, 2011 Kelmen

is that a service pack or service break?

Tue, Mar 29, 2011 Robert Northern California

Yes. I have agreed with these people that VS2010 SP1 runs very slow and scracthed many times. I have unstalled it.

Mon, Mar 28, 2011 John Marx Michigan City, Indiana

The "breaking" of Microsoft SQL Server Management Studio for intellisense is beyond unacceptable. Ready to wipe my entire system and skip the service pack even if it does fix somethings what it breaks is even worse.

Wed, Mar 23, 2011 Travis United States, CA

Ignore below (code generation problem in SP1). The problem was me.

Wed, Mar 23, 2011 Travis United States, CA

Automatic Code generation is failing in silverlight client applications for Complex Entity Types defined in an Entity Framework Model. I'm working up a before sp1 / after sp1 video to show the problem.

Wed, Mar 23, 2011 Frank United States, CA

I lost support for importing stored procedures into an Entities Model. When I add as a complex type via import function it doesn't show up in domain service!

Wed, Mar 23, 2011

I am a programmer of 12 years I have always used Microsoft products until now, after all this time I realized that 60 percent of my time I spend fixing code to work with new service packs or releases. It has sent me broke, I now use Java, PHP, and open source. I cannot understand how Microsoft get it so wrong. I use the Intellij idea IDE it leaves the Microsoft product for dead. Dear Microsoft maybe you need to concentrate on your loyal customers before they all do what I have done, ps I am buying my first Mac for similar reasons

Mon, Mar 21, 2011 rooshan China

When I use vs2010 sp1 working in the silverlight business application, from XAML file to 'Behind Code' file is to slow, I think there is a bug! could any one see the problem? any help would be very thanksful!

Mon, Mar 21, 2011 Krishna Kumar Bengalore

I have installed the VS2010 SP1 which is behaving worse than earlier, why MS release this type of SP's. The editor become too slow and it is hanging to type any statements. I am going to rollback soon.. Please update is any fix available. The intellicense is consuming lot of time... VS2010 SP1 is hell.

Mon, Mar 21, 2011 Raja Venkatesh Chennai, India

Post VS2010 SP1Rel, VS crashes with error in module "MSVBIDE.DLL". Unable to open any project with VB source code. All our projects are VB and we had to rollback immediately.

Sun, Mar 20, 2011 Michael Knight London

As a senior software developer in the city we had high hopes for the recent SP1 roll up. My team on the language had reported mixed emotions with the update. The C# section appear to be satisfied with the release on all platform (, WPF, Silverlight..) However the VB team reports only projects have not been affected but the rest Silverlight/WPF and Winform are being affected(People were sent home, All day wasted trying to roll back with previous setting). Clearly there is a pattern here Microsoft seems to be forcing developers to migrate to C# and this has been happening since 2006 by not improving VB crucial functionalities that C# already supports, even simple keywords like Yield and ton others are not supported. In plain word THEY AREN'T BOTHERED! This releases cost allot of companies money and this release was a dud != the impact we were all hoping for, alright ahah give us the real one, I'm serious! Those cash strapped, Fat cats - software quality engineers guys are all on vacation I guess...

Fri, Mar 18, 2011 Dan

As a C# person that needs to use SQL all day long and write code, VS is full of bugs. Sql management studio is simply broken, custom keyboard bindings in the editor no longer work, nor am i able to set them. The editor really sucks more than before. The window buffer after completing a few lines of text the editor flashes as it redraws, it appears to be collapsing and expanding all the text in the window not sure why, outline mode is off. While the biggest annoyance is selecting text you can't. Trying to select lines (Shift UP/Down Arrow), nothing is selected, string shift pgup/pgdn will work. You think you'd expect more from a product that cost 1000's of dollars, good thing my company bought it, not my money. Worse part commenting in the MS forums all the "MSFT" people that replay defend the behavior changes you see in VS 2010, i've watched as each new release of VS just gets worse and worse.... How about rolling back to 2008 and getting rid of the BS WPF editor for starters...?

Thu, Mar 17, 2011 Chris Poland

I also can confirm some performance problems, especially during build and running the debug mode. (CPU usage spikes to 100% and remains there for sometime, even though I'm doing nothing.) I think this only happens after some time running VS, but it doesn't seem like a memory issue, at least for me.

Wed, Mar 16, 2011

Won't install on W7/64: "The setup cannot be run in compatibility mode"

Wed, Mar 16, 2011 Sunil India

VS 2010 SP1 has broken our post build events. The $(TargetPath) value has changed. The $(TargetPath) is generally a summation of $(TargetDir)$(TargetFileName); but now it is taking $(ProjectDir)$(TargetFileName).

Wed, Mar 16, 2011 Bryan Alabama

I work mostly with and I've not noticed any issues. I've also not really noticed any significant improvement. That could be because I'm stuck running it on XP Pro sp3.

Wed, Mar 16, 2011 Matthew California

After installation of VS2010 SP1, we can no longer view build information from our TFS2008 server. Visual Studio 2010 immediately closes when you double click the build. A google search revealed that others are also experiencing the same problem.

Wed, Mar 16, 2011 Sean Columbus Ohio

VS 2010 SP1 causing our WinForm app to run extremly slow in debug mode, several seconds between clicks being registered on main UI thread. The same debug version runs fine when ran outside of VS IDE. Uninstalling!

Tue, Mar 15, 2011 danny Seattle

I installed SP1 and haven't had any problems. VS2010 pre-SP1 did crash occasionally when cut & pasting where the source is outside VS, but it seems pretty stable with the C# stuff I do.

Tue, Mar 15, 2011 AWebb Virginia

Installation Did Not Succeed. Because ... "The system cannot find the file specified" "Patch (C:\DOCUME~1\AWebb\LOCALS~1\Temp\Microsoft Visual Studio 2010 Service Pack 1_10.0.40219\VS10sp1-KB983509.msp;C:\DOCUME~1\AWebb\LOCALS~1\Temp\Microsoft Visual Studio 2010 Service Pack 1_10.0.40219\VC10sp1-KB983509-x86.msp) Install failed on product (Microsoft Visual C# 2010 Express - ENU). Msi Log:
[3/15/2011, 18:19:8]MSI returned 0x2

Tue, Mar 15, 2011 Stephen England

Just to say to any interested readers that Diego is being very helpful. We do still have some issues with VS2010 compatibility with our VS2005 codebase but they are not insoluble and largely due to VS2005 not correctly following the STL standard where VS2010 does. As such this is not a fault in VS2010 but of VS2005. We are now hoping to move to VS2010 once all issues can be sorted.

Mon, Mar 14, 2011 Diego Dagum Redmond, WA

Hi Stephen! I'm Program Manager with the MS Visual C++ team. We are sorry to hear your experiences with the product and would like to help. We need more information to reproduce your scenario and investigate further on what it's causing those. Can you please contact me at We'd really appreaciate it. Thanks!

Mon, Mar 14, 2011

I finally got a chance this weekend to use the SP1 that I had installed earlier in the week on my own systems (we're stuck with VS 2008 at my day job). I didn't notice any slowdown or anything. What I did notice, however, was the vastly improved help client. It is so far superior to whatever browser based thing they had before. Big improvement.

Sat, Mar 12, 2011 Dave Crozier Manchester

I installed the SP1 on release day and VS now runs slower than before and I keep getting out of memory errors that didn't happen before. The loss od SQL intellisense is annoying to say the least. One thing they haven't fixed which in my mind is a real pain is the inability to detach the toolbars from the main screen even though they all imply they float. In VS2003, 5 and 8 I have always used floating toolbars especially the Debug one and it stinks that you cant "float" anything. Evidently this is by design as the rewrite uses WPF which would have meant major rewrite, but why give the impression that the toolbars float if they can't. Strikes me that a LOT of work needs to be done before VS2010 is ready for prime time. I'll stick to good old trusty 2008 for now thank you.

Sat, Mar 12, 2011 Stephen England

I'm pleased it works for some people Brad. But I only expect to start an IDE once a day so start up time is an irrelevance and most of the "valuable features" are of no interest to us and generally what I would call bloat that I would like to turn off. What is important to me is that it can compile our code quickly and produce good output. Code that passes happily through three other compilers, including earlier Microsoft ones, without constant internal compiler errors and the unfriendly advice to "try simplifying or changing the program near the locations listed above".

Fri, Mar 11, 2011 Steve Utah

I just installed SP1 and now I can't debug a dll in my project that is called by an external application. I am using ironruby to run cucumber tests which calls a dll in my project. This worked fine until I installed the service pack.

Fri, Mar 11, 2011 Brad

It's not that bad. We've been using VS2010 every day on large applications since it was released. It launches quickly, works great, and has tons of valuable features (though I'm sure it uses a lot of resources). We've all been experiencing the "out of memory" error that forces you to restart it, but that has been a minor annoyance.

Fri, Mar 11, 2011 Stephen England

I'm a software architect in a large multi-national engineering company which uses a lot of C++ but not C# or any other .NET languages. We had great hopes of SP1. We're still using VS2005 for Windows and would dearly like to update to a more modern compiler on that platform. Sadly SP1 fixes absolutely none of the issues we have had with VS2010. 1. It is still really slow and a terrible resource hog. 2. It cannot build large projects or solutions without crashing or seizing up. 3. Appears to have issues with some template constructs which compile cleanly on the highest warning levels in both VS2005 and GCC 4. 4. It cannot import old projects correctly, namely $(OutputDir) is wrongly parsed, a relatively easy fix but shows lack of testing. I suspect most of these problems are related to the new build system and use of .NET. I think we're going to have to give up and stick with 2005 indefinitely. Tragic, what a mess, I trust it is better for the C# people.

Add Your Comments Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Please type the letters/numbers you see above

.NET Insight

Sign up for our newsletter.

I agree to this site's Privacy Policy.