Visual Studio 2005 SP1 released

Visual Studio 2005 SP1 released

  • Comments 57

The Visual C++ team is excited to announce the release of Visual Studio 2005 SP1!!!  The Service pack launched on Friday December 15, 2006 and is available for download here: VS2005SP1   This SP addresses issues that were found through a combination of customers and partner feedback, as well as internal testing. There are over 400 Visual C++ bugs that have been fixed with issues ranging in severity from minor syntax highlighting problems to customer reported crashes across various scenarios. In some areas, more than 50% of the bugs addressed were reported by customers through the MSDN Product Feedback Center and Microsoft Connect. Overall, Service Pack 1 offers customers improvements in responsiveness, stability and performance for Visual Studio 2005.


Service Pack 1 also provides over 70 improvements for common development scenarios including:

  • New processor support (e.g., Core Duo) for code generation and profiling
  • Performance and scale improvements in Team Foundation Server
  • Team Foundation Server integration with Excel 2007 and Project 2007
  • Tool support for occasionally connected devices and SQL Server Compact Edition
  • Additional support for project file based Web applications
  • Windows Embedded 6.0 platform and tools support

For developers using Visual Studio 2005 on Windows Vista, Microsoft is in current development on an update to Service Pack 1 called the ‘Visual Studio 2005 SP1 Vista Refresh Beta’. This update builds on the improvements made in SP1 and delivers a first class experience for developers wanting to take advantages of the new features in Windows Vista. The Visual Studio 2005 SP1 Update for Windows Vista is expected to ship after the consumer availability of Windows Vista in Q1 of 2007 and is now available in beta.

  • See for information on how to create a slipstreamed VS2005 SP1 installation.

  • Does SP1 include a new VC++ redistributables package (vcredist_x86)?

  • Two problems with SP1 for visual C++ that caused me to have to uninstall it.  I have a pure win32 c++ application.

    1. Couldn't compile anymore because of problem in xutility.  I used the workaround to copy the CE one over it and that worked for me.

    2. Couldn't redistribute it - got the dreaded error 14001 error when try to run on a client machine.  Manifest problem?  Couldn't find a workaround for this, had to uninstall.

  • A VS.2005 bug (not present in previous VS versions) regarding IntelliSense locking the IDE with 100% CPU usage when trying to parse recursive templates in C++ was tracked about half a year ago (symptoms virtually identical to a C# bug fixed in SP1 described here: As for the C# version it was reported as known and a hotfix was available through customer support (which however never answered my request for the fix), and was said to be fixed in a forthcoming service pack.

    Now I cannot find the bug in the database anymore, but the bug is still present in SP1 and the IDE locks up on on all files where the recursive templates are included or used.

    Why has the bug not been fixed when it was known, of severe nature, and a virtually identical C# bug has been addressed? Why is (if it is) the bug record missing from the database?

    Since much of my code relies on template composition I'm currently forced to edit certain (many) files in external editors, which is an untenable situation. I do not want to be forced to change environment, but am feeling increasingly forced to.

  • Can someone confirm if bug 101425 is fixed in

    Visual C++ 2005 SP1?  The bug report is at

    I can't find this bug or its duplicate bug 98949

    in the list of bug fixes:

  • Hey guys,

    you can find a list of the fixed bugs here:

  • I am actually using Windows Vista Ultimate.

    I installed VS2005 but it says that it has

    Problems with compatibility.

    I tried the SP1 for Vista Beta, but it says,

    that it was not able to find installation.

    Any tips??

  • SP1 returns this error:

    C2590: '()' : only a constructor can have a base/member initializer list

    on any function level try blocks.

    Anyone reading this and contemplating installing, don't. It's seriously broken, even at the grammar level.

  • Well, with not a little bitterness I have to say that many of the bugs that should have been fixed in SP1 will likely be fixed in SP2, which we'll probably get somewhere around mid-2008.

  • when i try to open a file using fopen, i got error message indecating that this functio need mor arguments, while i used to use only 2 arguments in the dot net version.

  • I installed the beta release to this service pack and i also discovered that there was a problem with the manifest. Applications that were compiled under the older version of vcredist_x86 do not start anymore!!

    Also a installer made with Visual Studio didn't detect this problem on a client machine so it didn't install the latest vcredist_x86.exe. It installs everything fine on a clean machine...

    but applications that are compiled without SP1 don't run on this machine.

  • The header file "xutility" in the "Microsoft Visual Studio 8\VC\include" directory is out of sync with the same file in "Microsoft Visual Studio 8\VC\crt\src" this is causing error's like "unknown override specifier". Solution is to copy the header file into "Microsoft Visual Studio 8\VC\include"

  • After all these years MS has finally created the most complicated piece of crap ever.  You've over engineered the most simplistic stuff and finally made everything break and no one can understand it anymore.  I would rather spend my time learning unix and recoding a project then deal with the manifesto created by requiring a manifest for win32 an c++ projects now.

    And most of this doesnt work to begin with.

    Let's see went from just including msvcr80.dll locally in an apps directory to now having to run vcredist_x86.exe, and reboot.  But, wait, there's a whole list of os's and conditions where this will not work.  You may also have to have the user validate there system, and run windows installer 3.1.  But wait there's a bunch of conditions where this wont' work either. Even tried MS's "Deploying Visual C++ library DLLs as private assemblies" but alas, that did not work either. So instead of a simple install MS has created another mess on top of its existing mess. Wonder when the last time Bill tried to code something?  He's probably using linux...

  • Quote from: art

    "Wonder when the last time Bill tried to code something?  He's probably using linux..."

    He probably got smart and started using a Mac.

  • We are deploying the MFC and CRT dlls as private assemblies. It works fine with the Visual Studio 2005 (no SP).

    The directory structure is :








    After installing the SP1 for Visual Studio 2005 the old deployment scenario does not work anymore. There is an error in event viewer :

    Dependent Assembly Microsoft.VC80.MFCLOC could not be found and Last Error was The referenced assembly is not installed on your system.

    So I have copied also the MFCLOC assembly to the destination directory. After that another errors appears in event viewer:

    Component identity found in manifest does not match the identity of the component requested.


    Syntax error in manifest or policy file "W:\deploydir\Microsoft.VC80.MFCLOC.MANIFEST" on line 5.

    The assemblies are copied from the

    C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\ directory.

    Is the MFCLOC manifest corrupted?

    What should I do to get it work?

    The above mentioned problems occurs only on XP SP2. On Win2000 the old deployment scenario is still working.

Page 2 of 4 (57 items) 1234