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:
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.
Our app no longer runs under XP after recompiling with SP1. Well, it DOES run immediately after installing if you don't reboot. After rebooting it fails with error 6301 "attempt to load CRT more than once; this indicates a bug in your app"! This never happened prior to SP1, the app works on macjines with dev studio installed and also on vista machines! I'm hoping that it's just that the new sp1 redist hasn't been used in the install, I'll try it on monday. Distressing that so much (mysterious) trouble is caused by installing the service pack.
This update blows! I'd rather have the 400 c++ bugs than this steaming pile. Whoever came up with the manifest system is a moron. It has given me nothing but grief from the beginning. Now that I have applications finally working, the latest upgrade ruins it again. The biggest BUG Microsoft needs to fix is this flawed system that makes it impossible to let other people run your own software.
By the way, I'm uninstalling the update ... hope it works.
On vista with SP1 and the Vista update for SP1 I have the following issues:
- No drag and drop from explorer. I can workaround this by running an elevated explorer but I shouldn't have to.
- Double clicking on a .CPP file opens VS2005 but no file opens in it! I have no solution to this problem.
What's wrong with 2005 and Vista? I got Vista on my new laptop (I wanted XP) and I must say, as far as VS2005 is concerned, it all but unusable.
Please make a signed vcredist_x86-SP1.exe available from Microsoft.com.
Otherwise, I'll be forced to convert all my projects to another solution such as gcc (Mingw32) or Borland Turbo C++ 2006 Explorer (free).
Hey, does anyone from Microsoft read these comments? Here's the short and sweet of it. I built applications that ran fine for months. Then I installed SP1. Applications won't run any more on client's machines (The application failed to start because the application configuration is incorrect. Re-installing the application may fix the problem.) Sound familiar?
SP1 should be renamed "Disservice Pack 1". I don't have the time to screw around trying to fix problems introduced by Microsoft. I removed SP1 and everything runs OK. I can live without it.
Microsoft appears to be more interested in promoting their C# than paying attention to C++ issues. Why does that not supprise me?
We are trying to convert our application from VC++ 6.0 to VC++ 8.0 (as recommended by Microsoft) for fixing thread safety issues in STL. Compilation of several modules fail with xutility errors (we do not explicitly include xutility in any of our files). These errors (C2988, C2059, C2143, C2447) persist even after applying SP1.
Can anyone help, please ?
very "funny" this problem. In MFC Application or DLL's I link now CRC and MFC with static options.
But when I build a C++.cli assembly a have no chance to do that. Why different MSCVRTxx, MFCxx DLL's have the same name ???, DirectX DLL's have very different names and different applications versions can life together.
WinSxs policies,manifests ... is not right way.
Can any body tell me how I can remove the stupid SP1 ? My customers waiting for solutions !
What the hell are they smoking at Microsoft. These manifests are more screwed up then the old way.
First off how could their own manifest tool embed two different versions of the same file. Which portion of my dll is going to know which version to use.
Secondly it looks like it isn't even smart enough to embed the versions that are currently in the toolkit folders. Hence if I wanted to use the non SP files wouldn't I just copy the old ones in there and it would pick up that those are the ones I want to use.
Thirdly how does this solve anything. If they update the files in the future and publish a new policy what says I know my program is going to work properly with the new files. I want it to still work with the ones I know it works on but they are going to force it to use the new one.
My original background is engineering and from that we learned about things called revisions. Why not put a revision line mfc80a.dll on the new files and let us link to those as it is. In our field you still keep the old ones around and if you're making a replacement part for a machine that used the Revision B or a part you grab that drawing and make the part from that. If you're building a new machine then you double check that everything is going to work and use the new revision.
I wish I never would have let you main programmer talk us into porting up to VS 2005.
It takes some planning but you can fit your favorite foods into your meal
plan and still manage a healthy life style for your entire family. For starters,
you should try this [url=http://artmam.net/Dir-Chicken_Recipe.htm]chicken recipe[/url].
I have tried many times now to install SP1 on a XP x64 machine, and I am having no luck.
Core 2 Duo 6600
4 GB RAM
XP x64 SP2, fully patched
When I try to run the installer, the standard MSI dialog 'Preparing to install' is shown, but then after about 30 min the system just says 'Install server not responding'. Seems like a fairly unique thing, I cannot find similar stuff on the web.
Any ideas? We have already reinstalled 3 times (it is a new machine anyway), without luck.
Solved the problem.
The SP1 installation finished after I installed a security update (KB-925674). So it was either that or our Antivirus, Sophos (which I traced to other problems as well).