Re: regsvr32 error code 0x80004002



Hi Norman,
Thanks for your response.

I think that this issue was caused by assembly redirection. Since .NET 3.0
SP1 was installed, the Microsoft.VC80.CRT assembly was redirected to the
newest version according to policy file which you can find in
%Windir%\WinSxS folder, however according to your DLL manifest, your
assembly should reference the old version. This may caused this error.

I recommend that you first try using private assemblies to see if it helps.
Manually copy the related DLLs and manifests to your COM application folder
and rename the manifest file according to this article:
Private Assemblies
http://msdn2.microsoft.com/en-us/library/aa375674.aspx

Regarding redistributing VC++ DLL as private assemblies, you can also refer
to the following articles:
Redistributing Visual C++ Files
http://msdn2.microsoft.com/en-us/library/ms235299(VS.80).aspx
Choosing a Deployment Method
http://msdn2.microsoft.com/en-us/library/ms235316(VS.80).aspx

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================







.



Relevant Pages

  • Re: Deployment, side by side assemblies
    ... dissasembler component and configure it to use 1 specific schema. ... > assembly redirection, biztalk engine failes to create the ... > Target Site: Void RunClassConstructor ... > assemblies with the same schema where only the assembly ...
    (microsoft.public.biztalk.general)
  • Re: ProgID in .NET?
    ... To use a config file approach for assembly redirection, ... To give assemblies a strong name: ... SvenC ...
    (microsoft.public.dotnet.languages.vc)
  • Re: VSTO 2005 solution deployment
    ... Deployment of Office solution is quite large topic. ... classes) need to be loaded by using a special VSTO manifest file. ... OfficeStartupClass assembly attribute), location of assemblies, ... projects are compiled VSTO will embed a special ActiveX control into ...
    (microsoft.public.vsnet.vstools.office)
  • Re: At wits end dealing with "Assemblys manifest does not match assembly reference". Need help under
    ... Q1) Under what conditions can a mismatched version error manifest? ... This is normally a problem when your DLL is compiled. ... Look for circular references. ... When the test program builds it, of course, copies the assemblies ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: At wits end dealing with "Assemblys manifest does not match assembly reference". Need help under
    ... reference to two projects but the projects have the same project GUID. ... Q1) Under what conditions can a mismatched version error manifest? ... This is normally a problem when your DLL is compiled. ... While this is true for each of the assemblies, it is not true for the test ...
    (microsoft.public.dotnet.languages.csharp)

Loading