<comClass> entries sometimes are omitted

[DaveInCaz]

On occasion when we run UMMM for our project, for a given DLL there will be no <comClass> entries added.

It seems like this has occurred in cases where an older version of the DLL was registered on the PC which had conflicting CoClass GUIDs.

Specifically, in pvDumpClasses the expression

LenB(pvRegGetValue("CLSID" & .Guid & "\InprocServer32")) <> 0

results in FALSE.

I'm curious however why this is a problem. My initial impression was that UMMM relies only on information in the actual DLL file - but it seems that registry information is also taken into account?

Thanks

[wqweto]

UMMM uses both typelib from dll/ocx files and registry entries to construct manifest xml. Which means that dll/ocx files have to be registered before generating project manifest.

Implementing registry redirection and shelling dll/ocx registeration from UMMM was an option that I weighted potential risks on not implementing. As of now it just relies on output binaries being freshly compiled on build machine before final project manifest being generated.