Visual C++ Team Blog

Can Vista users install SP1 now or do we have to wait until Q1?

Where I can find list of fixes?

Is there a list fixes for SP1 somewhere? I reported a pretty nasty bug in the C++ code editor. It was marked as fixed in October, but it still occurs in SP1.

https://connect.microsoft.com/feedback/viewfeedback.aspx?FeedbackID=183708&wa=wsignin1.0&siteid=210

I downloaded the service pack, but (unfortunately) it does not work. I tried to install it to XP SP2 (32 bit) and Win2k3 SP1 (32 bit) but it fails with error that windows installer did not configured properly.

I'm also looking for a list of fixes.

A search for visual studio 2005 fixlist did not yield any useful results :-(

Thanks for the posting the link to the fix list.

I cant install this SP1, i dont have enought hard drive space!!!!

See http://blogs.msdn.com/heaths/archive/2006/12/16/slipstreaming-visual-studio-2005-service-pack-1.aspx for information on how to create a slipstreamed VS2005 SP1 installation.

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.

Can someone confirm if bug 101425 is fixed in

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

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=101425

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

in the list of bug fixes:

http://support.microsoft.com/default.aspx/kb/918526.

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??

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.

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.

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.

http://msdn2.microsoft.com/en-us/library/ms235542(VS.80).aspx

http://msdn2.microsoft.com/en-us/vstudio/aa718685.aspx

http://forums.winamp.com/showthread.php?s=&postid=2097354#post2097354

http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx

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...

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 :

mfc80u.dll

Microsoft.VC80.CRT.manifest

Microsoft.VC80.MFC.manifest

msvcp80.dll

msvcr80.dll

MyApplication.exe

MyDll.dll

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.

and

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.

How to add .C file in VS 2005 with my existing Application .

thanks

sabari

Hi Shahid

The file is located in folder:

C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86\

I have the VS Standard Edition installed but I think it is not installed when you use the Express Edition.

In addition there is no direct link (AFAIK)  from Microsoft to download this package.

Hello.

I tried relinking CRT library and error occurrs during it. This error occcurrs due to -wx witch (warnings as errors). If this switch is erased,

relinking is stopped due to *.obj is missing. I am beginner in nmake script syntax.

Can you help me, please.

---------------------------------  problem ---------------------------------

Generating Code...

cl -D_CRT_NOFORCE_MANIFEST -D_STL_NOFORCE_MANIFEST  -O1 -Zi -Wp64 -D_X86_ -I.

-Fobuild\intel\mt_obj\ intel\fp8.c

fp8.c

link -lib -nologo -wx -out:build\intel\mt_obj\startup.lib

@build\intel\mt_obj\startup.rsp

wincrt0.obj : warning LNK4006: __aenvptr already defined in wwincrt0.obj;

second definition ignored

LINK : error LNK1218: warning treated as error; no output file generated

--------------------------------- End of

recompiling ------------------------

Generating Code...

cl -D_CRT_NOFORCE_MANIFEST -D_STL_NOFORCE_MANIFEST  -O1 -Zi -Wp64 -D_X86_ -d1Binl

-EHsc -GR -Istdhpp -I. -Fobuild\intel\mt_obj\cpp_obj\ /TP strftime.c

wcsftime.c

strftime.c

wcsftime.c

Generating Code...

link -lib -nologo -wx -out:build\intel\mt_obj\time.lib

@build\intel\mt_obj\time.rsp

copy intel\mt_lib\conv.lib build\intel\mt_obj\conv.lib

       1 zkop?rovanech soubor.

copy intel\mt_lib\tran.lib build\intel\mt_obj\tran.lib

       1 zkop?rovanech soubor.

copy intel\mt_lib\matherr.obj build\intel\mt_obj\matherr.obj

       1 zkop?rovanech soubor.

st, I 31 2007 10:16:06             build\intel

st, I 31 2007 10:16:18             build\intel\mt_obj\convert.lib

st, I 31 2007 10:16:21             build\intel\mt_obj\direct.lib

st, I 31 2007 10:16:27             build\intel\mt_obj\dos.lib

pá, XII 01 2006 22:54:18             build\intel\mt_obj\eh.lib

st, I 31 2007 10:16:36             build\intel\mt_obj\exec.lib

st, I 31 2007 10:16:42             build\intel\mt_obj\heap.lib

st, I 31 2007 10:16:42             build\intel\mt_obj\helper.lib

st, I 31 2007 10:17:00             build\intel\mt_obj\lowio.lib

st, I 31 2007 10:17:24             build\intel\mt_obj\mbstring.lib

st, I 31 2007 10:17:44             build\intel\mt_obj\misc.lib

pá, XII 01 2006 22:54:18             build\intel\mt_obj\rtc.lib

                                     build\intel\mt_obj\startup.lib target

does not exist

Thank for your help.

BEST regards Honza.

We NEED the vcredist_x86-sp1.exe and vcredist_x64-sp1.exe available in Microsoft's downloads page omg!

Also there is a problem when you create a Windows Installer project... It appears the x64 VS runtime DLLs version is not launched correctly.

pls solve it

I found this as well, and obe way round it is to go to Solution/Properties/C/C++/Code Generation and set the 'Runtime Library' field to 'Multi-threaded (/MT)' or 'Multi-threaded Debug (/MTd)' rather than 'Multi-threaded DLL (/MD)' or 'Multi-threaded Debug DLL (/MDd)'.

This does bloat your final app by including all the required run-time, but does mean it will run without needing the redist package.

Wim

I've read this thread with interest but I'm still not certain why I can't redistribute my app. I'm using MSVC 2005 pro with SP1 installed. To deploy on a machine without msdev I run vcredist_86.exe and copy across the relevant processor-specific files to the root of the folder with my exe as described: http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx (Deploying Visual C++ library DLLs as private assemblies)

Problem is; the release version of my exe runs, and the debug version doesn't. I need to run the debug version for internal testing. When I run the debug version I get the dreaded "The application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem" error.

I've had a look at the event viewer at the debug app that failed to run and I find the error "Syntax error in manifest or policy file "C:\testapp\Microsoft.VC80.DebugCRT\Microsoft.VC80.DebugCRT.manifest" on line 4. This is odd, as I got it from the MSVC vcredist folder.

I've installed the latest redist package on the target machine http://www.apachelounge.com/download/vcredist_x86-sp1.exe

As I've said the release version works fine, the debug doesn't.

Thanks in advance for any help ;)

Finished the upgrade to VS2005, and I've got to say I am presently disappointed in this product. I want to distribute a simple command line tool to the field. It works OK under test, since the manifest file is in the same directory as the exe. However, if the exe is run on another machine, it complains that the CRT was improperly loaded and fails. So, I thought, well let's embedd the manifest in the exe and be done with it right? Wrong! Now I get a build error:

error PRJ003: Error spawning 'cmd.exe'.

This goes away if I don;t embedd the manifest, but then I have to distribute the XMl file with the exe, which I don;t want to do...

Any Ideas?

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.

By the way, I'm uninstalling the update ... hope it works.  

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).

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 ?

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.

I have tried many times now to install SP1 on a XP x64 machine, and I am having no luck.

System:

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.

Thanks,

JC