EDN Admin
Well-known member
<div class=codeseg>
<div class=codecontent>
I did a fresh install of the 90 day trial of Visual Studio Professional and am immediately unable to get a basic C++ application to work in the debugger. I get the following error dialog (entitled "myapp.exe - Unable To Locate Component"):
"This application failed to start because MSVCR90D.dll was not found. Re-installing the application may fix this problem."
There is no problem at all if I just run in release mode.
It doesnt get any simpler than what Im trying...
<ol>
Install VS 2008 Pro demo
Create a new C++ project (myapp) that is a simple Win32 console application
Leave everything as defaults (including _boilerplate _tmain() definition... not even adding a "Hello, world!")
Click the play button (in debug mode to make it go)
Build completes successfully
Error message pops up</ol>Ive tried it on two systems so far and the exact same thing happens on both. The only potential for confusion I can imagine is that I had VS8 Express on the systems, and some other MS SDKs that I dont recall offhand because I have since purged the machine and re-installed everthing to try and make this go away. If it matters, the SDKs I had installed were only to try and get the MFC libraries which I found out were missing in the express edition, which is why Im now trying to demo the pro version which has them. It shouldnt matter, but to be thorough and highlight that it is not one corruptes system Im dealing with Ill also state that one of the systems I tried it on (this one) is a dedicated XP machine, while the other was an XP virtual machine on completely different hardware.
Ive been looking at this for a few days now and have found only a few referenced to this problem. None have helped me, but these are the most relevant:
http://preview.tinyurl.com/44o3sy
http://preview.tinyurl.com/4po38x
There have been several references to the manifest file... here is the manifest file generated:
<div style="text-align:left
<div class=codeseg>
<div class=codecontent>
<div class=codesniptitle><span style="width:100% Code Snippet
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false </requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.DebugCRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b </assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>
Ive searched my pc and found msvcrtd.lib in two locations:
C
rogram FilesMicrosoft Visual Studio 9.0VClib
Crogram FilesMicrosoft SDKsWindowsv5.0LibIA64
and Ive found msvcr90d.dll in these locations:
C:WINDOWSWinSxSx86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456
Crogram FilesMicrosoft Visual Studio 9.0VCredistDebug_NonRedistx86Microsoft.VC90.DebugCRT
When I check "Tools->Options->Projects and Solutions->VC++ Directories->Library Files" I have the following folders listed:
$(VCInstallDir)lib
$(VCInstallDir)atlmfclib
$(VCInstallDir)atlmfclibi386
$(WindowsSdkDir)lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
Ive tried adding the directories where I found msvcrtd.lib and msvcr90d.dll to the list of VC++ library directories, but it doesnt work. Trying to run the debugger still gives the indicated error.
Any help appreciated in getting the debugger working!! Im not totally immobilized because i can still build "release" loads and work with them, but Im resorting to scattered printfs in my code and I feel like Ive time warped back to the 80s.
How could this not be working with a fresh install of the demo (on two machines!)... it certainly hasnt been a very good demo so far!
Russ
View the full article
<div class=codecontent>
I did a fresh install of the 90 day trial of Visual Studio Professional and am immediately unable to get a basic C++ application to work in the debugger. I get the following error dialog (entitled "myapp.exe - Unable To Locate Component"):
"This application failed to start because MSVCR90D.dll was not found. Re-installing the application may fix this problem."
There is no problem at all if I just run in release mode.
It doesnt get any simpler than what Im trying...
<ol>
Install VS 2008 Pro demo
Create a new C++ project (myapp) that is a simple Win32 console application
Leave everything as defaults (including _boilerplate _tmain() definition... not even adding a "Hello, world!")
Click the play button (in debug mode to make it go)
Build completes successfully
Error message pops up</ol>Ive tried it on two systems so far and the exact same thing happens on both. The only potential for confusion I can imagine is that I had VS8 Express on the systems, and some other MS SDKs that I dont recall offhand because I have since purged the machine and re-installed everthing to try and make this go away. If it matters, the SDKs I had installed were only to try and get the MFC libraries which I found out were missing in the express edition, which is why Im now trying to demo the pro version which has them. It shouldnt matter, but to be thorough and highlight that it is not one corruptes system Im dealing with Ill also state that one of the systems I tried it on (this one) is a dedicated XP machine, while the other was an XP virtual machine on completely different hardware.
Ive been looking at this for a few days now and have found only a few referenced to this problem. None have helped me, but these are the most relevant:
http://preview.tinyurl.com/44o3sy
http://preview.tinyurl.com/4po38x
There have been several references to the manifest file... here is the manifest file generated:
<div style="text-align:left
<div class=codeseg>
<div class=codecontent>
<div class=codesniptitle><span style="width:100% Code Snippet
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false </requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.DebugCRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b </assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>
Ive searched my pc and found msvcrtd.lib in two locations:
C
rogram FilesMicrosoft Visual Studio 9.0VClibC
rogram FilesMicrosoft SDKsWindowsv5.0LibIA64and Ive found msvcr90d.dll in these locations:
C:WINDOWSWinSxSx86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456
C
rogram FilesMicrosoft Visual Studio 9.0VCredistDebug_NonRedistx86Microsoft.VC90.DebugCRTWhen I check "Tools->Options->Projects and Solutions->VC++ Directories->Library Files" I have the following folders listed:
$(VCInstallDir)lib
$(VCInstallDir)atlmfclib
$(VCInstallDir)atlmfclibi386
$(WindowsSdkDir)lib
$(FrameworkSDKDir)lib
$(VSInstallDir)
$(VSInstallDir)lib
Ive tried adding the directories where I found msvcrtd.lib and msvcr90d.dll to the list of VC++ library directories, but it doesnt work. Trying to run the debugger still gives the indicated error.
Any help appreciated in getting the debugger working!! Im not totally immobilized because i can still build "release" loads and work with them, but Im resorting to scattered printfs in my code and I feel like Ive time warped back to the 80s.
How could this not be working with a fresh install of the demo (on two machines!)... it certainly hasnt been a very good demo so far!
Russ
View the full article