Hi, my name is Leslie Giblett and I’m a Release Manager on the Visual C++ team. As a Release Manager, I am responsible for insuring that the VC++ team releases a high quality product that tracks to our planned schedules. I work closely with our Management, Development and Quality Assurance teams to drive bug fixes and I work with related groups at Microsoft to release our product to customers. I also develop and maintain project milestones and set release definitions.
Our team is collaborating with the Visual Studio team for the upcoming VS2005 Service Pack (SP1) release. To keep customers better apprised of the changes, we are sharing the list of Visual C++ bug fixes included in SP1. Although this is not the final set of fixes, we already have our list of approved bugs and will not be accepting additional requests as part of this Service Pack. We are in the process of completing the work on these fixes and getting them ready for the Beta release. The lists below provide information on over 200 bug fixes listed by Bug title and Source ID (which is usually the customer name). Click on the bug title for a link to the Customer feedback URL. We hope to continue posting about the upcoming Service Pack - potentially listing QFEs and other fixes that will be included. The VS2005 SP1 release is a big win for our customers as it contains more fixes than any previous Service Pack.
Links to the list of fixed bugs can be found here:
Compiler Back End
Compiler Front End
Thanks and I hope you find this list helpful. Look for additional posts on this topic in the coming weeks.
Just blew a day tracking down problems in the new embedded manifest system for DLLs, right after wasting considerable time figuring out that VC8 can't generate import interfaces from complex COM objects correctly, such as PowerPoint's objects, and having to pull out VS6 to do it correctly. The IDE crashed daily (if not hourly) from intellisense until I reformatted all my template classes, and we won't even talk about the difficulties the time_t changes and trying to fix all the deprecation and security warnings caused.
It would be really nice if two things happened.
a.) A genuine bug tracker with vetted bugs were made available that developers could easily find and view, rather than an occasional post on some blog that's not exactly well linked to the product's pages...
b.) A little more testing prior to release. Development environments are mission-critical for many of us. I *hate* switching compilers, and when I am forced to switch, I'd sure like it to work at least as well as the previous revision (or in this case, 2 major versions back).
Unfortunately, my company upgraded to VC8 early - mainly due to the latest PSDK's not being compatible with anything else and the poor C# guys wanting the fixes in .NET 2.0. We're feeling the burn at this point, both in-house and when we ship to our customers.
I installed the Service Pack but now I have a big problem! If I compile my application using the patched VS and VC++ 2005, then I install my application into a PC where I installed the previous version of the run-time libraries (vcredist_x86 of not-patched VC++) the application DOESN'T RUN!
I have to uninstall the old vcredist_x86 package and install the new one. Why did you create this breaking with the previous version of VC++?
Do you plan to solve this problem with the final release????
Marco, just define _USE_RTM_VERSION in your project settings or near the top of your stdafx.h and it will use the existing versions.
I agree with what has been said multiple times before: Why is it that something as crucial as the list of fixed bugs and changes has to be found on some low-traffic blog without any link from the official SP1 pages? Relying on our development environment is essential during short build and release cycles, but it seems that the developers have been totally neglected with this. I work in a LARGE corporation and we need to assess the risk before we upgrade to SP1, but how can I assess anything if there is no detailed information on the changes?
The above links are from June 22, is there anything newer? Is that still the final list? Can please someone make this publicly available??
Thaks for the trick. But I have a question. Does a unluky developer to search any new Microsoft define in the .h include directory and try everything in order to make things to work?
Please, in the future write a complete documentation on how to use your SP.
OK I tried and I found a very big BUG!!!
The define _USE_RTM_VERSION works fine for executables but has no effect on a MFC dll. So If I have an executable using a dll I can define _USE_RTM_VERSION on both the exe and the dll, compile everything but when I try to run the exe it doesn't start because the dll try to bind the SP1 run time libraries.
The only way is to rebuild the dll without using _USE_RMT_VERSION and install the run time libraries of the SP1.
Yes, I noticed that the manifest of a wizard generated regular MFC DLL includes BOTH 50608.0 and 50727.762. Here is the generated manifest an MFC DLL.
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50608.0" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
<assemblyIdentity type="win32" name="Microsoft.VC80.MFC" version="8.0.50608.0" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
<assemblyIdentity type="win32" name="Microsoft.VC80.MFC" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
Seems like a bad bug, hopefully someone will figure out a workaround.
bug posted here
I posted a workaround on the bug report page.
I loaded SP1 (before reading this article) and my initial problems are still there
1) When trying to debug / step through the IDE could NOT find the mfc80d.dll (I know it is there..) so I had to copy it into the application folder, then it was missing another one etc... Seems strange that the IDE does not "Know" where its DLL's are
2) On exiting my application, it ASSERTS - AFTER my code, in both Release and debug mode and I can't figure out what / where...
Hope some can give me a hint here
I was hanging out in dotnet.languages.vc yesterday when I read an interesting question. Someone wanted
Where can one download the "Microsoft Visual C++ 2005 Redistributable Package" for SP1?
Specifically, I'd like for Chilkat customers to be able to download vcredist_x86.exe but for VC2005 SP1. A customer will typically download and install the Chilkat components on his/her development machine and the runtimes are installed because Chilkat includes the merge module for VC++ v8.0.50727.762. However, when redeploying to an end-user computer, the runtime is missing and you get the dreaded "This application has failed to start because the application configuration is incorrect."
I'll be grateful if an answer is emailed to firstname.lastname@example.org
[URL=http://english.edgewood.edu/eng259d2006/_disc24/00000349.htm?augmentin#">http://english.edgewood.edu/eng259d2006/_disc24/00000349.htm?augmentin#] augmentin [/URL]
[URL=http://fps.okstate.edu/_disc4/00005ebf.htm?desyrel#">http://fps.okstate.edu/_disc4/00005ebf.htm?desyrel#] desyrel [/URL]