Wednesday, September 17, 2008

Registration free COM for .Net and Native components

On XPSP2 it appears that manifests (assembly and application) need to be both embedded AND standalone.

 

The SideBySide assembly manager puts errors that occur during load into the System event log (on windows XP).  The errors are listed in reverse order so the last one is the most general and earlier ones are more specific.  This has proven invaluable in tracking down Side by Side assembly problems.  Apparently Windows Vista has an sxstrace tool that improves on this but I'm presently stuck on XP...

 

An error message along the lines of "Component identity does not match component requested" was, in my case, traced back to a missing "type=win32" attribute for the assemblyIdentity element.

 

 

No comments :

Post a Comment