"Ted" <te*@t--x.org> wrote in message
news:u1**************@TK2MSFTNGP15.phx.gbl...
I should also mention that there also should be a file in:
C:\WINDOWS\WinSxS\Policies\x86_policy.8.0.Microsof t.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773
named:
8.0.50727.42.policy
and there should be a line in there like this:
<bindingRedirect oldVersion="8.0.41204.256-8.0.50608.0"
newVersion="8.0.50727.42"/>
All information provided so far assumes you are using the RTM (i.e.
shipping) version of Visual Studio 2005.
Ted.
"Ted" <te*@t--x.org> wrote in message
news:uT**************@TK2MSFTNGP10.phx.gbl... It appears that your manifest is not getting embedded properly, or your
VC DLLs are not installed in the correct place.
That file should be in
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.DebugCRT_1fc8 b3b9a1e18e3b_8.0.50727.42_x-ww_f75eb16c
If you open up your EXE as resources using the resource editor, you
should see a manifest file RT_MANIFEST as 1. It should have references
to this DLL, something like this:
<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50608.0"
Ted.
Yes, this is the Visual Studio 2005 Professional Edition RTM, as downloaded
from MSDN.
I installed it on a third PC in my office and have the same behavior from
all three instances.
I have verified the file MSVCP80D.dll exists in the location you specify.
However, I also find a second copy of the file at:
D:\Program Files\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist\x86
\Microsoft.VC80.DebugCRT.
(Note: D: is the install drive, and the OS partition here.)
Could the second copy be causing the problem?
I have also verified the entry you cited in the 8.0.50727.42.policy file,
which is found in the location you specified.
However, when I looked in the debug folder for the .exe, there is no .exe to
be found, even though the output from build/rebuild shows 0 errors, 0
warnings, there is a link entry referring to the build log, where I find a
note indicating the .exe could not be found or created:
Compiling manifest to resources...
Linking...
LINK : E:\CIT1173\VS2005Test\Debug\VS2005Test.exe not found or not built by
the last incremental link; performing full link
Embedding manifest...
Results
Build log was saved at
"file://e:\CIT1173\VS2005Test\VS2005Test\Debug\BuildLog.ht m"
VS2005Test - 0 error(s), 0 warning(s)
But, no .exe!
So, it looks to me as if no executable is being created, but VS does not
consider that a problem?
I could swear this issue was not encountered in Beta 2, and creating empty
Win32 console projects, then having students create C++ programs to learn
language basics is essential to our classroom use of the product, just as
we've been doing with VS 6, VS.net 2002 and VS.NET 2003.
Sure hope there's a way to fix this.
