Merge Module woes with VS .NET 2005

I have an application which comprises several DLLs. All of the DLLs require manifests linking to common controls, ATL80 and MSVCRT80.

When I run the app on my machine I have no problems.

If I try and install it onto another machine it fails when it is self-registering the DLLs. If I look at the dependencies on the target machine I can see that it cannot locate ATL80 and MSVC80 and this is why it cannot load the DLL.

However, my second DLL, which links the same ATL80 and MSVC80 libraries loads in dependency viewer fine

. Both DLLs are compiled with ISOLATION_AWARE_ENABLED defined.

The installation was created in Wise for Windows 6 with the merge modules shipped with VS .NET 2005. I can see that they are a later version than the version stipulated in the generated manifest in my application.

The MSVC and ATL libraries are being installed into C:\Windows\WinSxS

Anyone got any ideas what the problem might be or ways I can diagnose what's happening

Thanks

Mark



Answer this question

Merge Module woes with VS .NET 2005

  • Tom Archer - MSFT

    Solved it myself - one of the dependencies wasn't installing correctly (MSXML4) so have removed it from the manifest for the timebeing since the merge module installs to windows\system32
  • Merge Module woes with VS .NET 2005