Manifest files for .net FW

[xwb]

I've built a C++/CLR DLL, xxx.dll with an embedded manifest on a .net FW2 system. It works fine with the executables on any system where .net FW2 is installed. However, if I put it on a system with .net FW3.5 (and .net FW2) it moans that something is missing.

Poked around with procmon and found that it wants xxx.dll.2.manifest. Presumably the 2 is for .net FW 2. Question 1 is why is it looking for a manifest file, even when the manifest is embedded in the DLL?

For some reason, I can't add this manifest file to the project resources. It says

A reference to 'xxx.dll.2.manifest' could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.

It is a valid assembly otherwise it wouldn't build.
Question 2 is what exactly is visual studio looking for?

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<dependency>
<dependentAssembly>
    <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>

 

[xwb]

Apparently this has been fixed on VS2005 SP1. Just installing SP1 now. No idea how long it takes: it has been unpacking itself for the last hour, CPU running at 100% and the fan is going like there is no tomorrow.

 

[xwb]

That didn't fix it. Still looking for a solution. Found quite a few hits on dlls and manifest files. I'll try chasing down those avenues.