Good tools for analyzing the interference of a COM object?

I have inherited two complex COM objects. One of them was obtained from the other and (presumably) GUID, etc., were changed so that they do not interfere. They interfere, and so far our debugging has not identified the culprit - we checked the registry differences and source code and looked at the SCCS checks. Obviously, we are missing something, but they are large and complex enough that I am not surprised.

Is there a tool that can help, perhaps by checking COM objects for good behavior or detecting collisions between two COM objects or analyzing the registry?

+1
source share
3 answers

Visual Studio, regcap, , GUID script. OLEView ( Visual Studio) .

, :
MMM (Make My Manifest) , VB.
Heat Tallow Wix 3.0 2.0 , - .

, , .

+6

, , , - RegEdt32.exe HKEY_CLASSES_ROOT - COM-, ID . CLSID HKEY_CLASSES_ROOT/CLSID, typelibrary. , , .

, , DLL. , Dependency Walker

+2
+2

Source: https://habr.com/ru/post/1702951/


All Articles