H
Howard Kaikow
I was playing with a COM example in an article at the MSFT web site.
This resulted in a DLL, call it x.dll, getting registered.
When I was done, I tried to unregister the dll using
regasm /u path\x.dll
Got an error, don't recall the text of the error.
So my fat fingers went into regedit and tried to delete all keys referring
to x.dll, other than those in the obvious MRU lists.
When I tried to delete, as I recall, the keys in HKCR, I was not allowed to
do so.
Rebooted and the keys were gone.
I figured that I must have screwed up as that was a mighty dirty process.
I copied x.dll, x.pdb, and x.tlb to D:\ to reduce fat finger errors.
I then used
regasm d:\x.dll
Checking the registry, I saw that the critter was registered.
Flush with my success, I then tried
regasm d:\x.dll /u
Sadly, that resulted in the same error as when I manually deleted the keys.
Rebooting caused the dll to become unregistered.
Obviously, I'm missing something.
How is one supposed to unregister a DLL, be it COM or not?
This resulted in a DLL, call it x.dll, getting registered.
When I was done, I tried to unregister the dll using
regasm /u path\x.dll
Got an error, don't recall the text of the error.
So my fat fingers went into regedit and tried to delete all keys referring
to x.dll, other than those in the obvious MRU lists.
When I tried to delete, as I recall, the keys in HKCR, I was not allowed to
do so.
Rebooted and the keys were gone.
I figured that I must have screwed up as that was a mighty dirty process.
I copied x.dll, x.pdb, and x.tlb to D:\ to reduce fat finger errors.
I then used
regasm d:\x.dll
Checking the registry, I saw that the critter was registered.
Flush with my success, I then tried
regasm d:\x.dll /u
Sadly, that resulted in the same error as when I manually deleted the keys.
Rebooting caused the dll to become unregistered.
Obviously, I'm missing something.
How is one supposed to unregister a DLL, be it COM or not?