PIA for custom Redemption.dll

[Jeff]

I made a custom Redemption dll using customize.exe, as explained at
http://www.dimastr.com/redemption/security.htm. I changed all the class
names and GUIDs. Let's say my custom Redemption dll is called
MyRedemption.dll. All the class names are the same except I prepended
them with "My". All the GUIDs are unique and not the same as those of
the standard Redemption.dll.

I then decided to make a signed, primary interop assembly (PIA) for
what I consider to be a brand new COM dll that I originated. I called
my interop Interop.MyRedemption.dll.

I registered MyRedemption.dll ("regsvr MyRedemption.dll").

I registered Interop.MyRedemption.dll ("regasm
Interop.MyRedemption.dll").

In a C# project, I added a Reference to MyRedemption.dll by Browsing to
it. However, the end result of adding that reference was that
"Redemption" appeared in my project's list of references, not the
expected "MyRedemption".

I thought by making a custom Redemption dll, there was no connection
between my custom dll and Redemption.dll, but that appears not to be
the case. I conclude based on the results of my test that there are
some common GUIDs between my custom dll and the standard
Redemption.dll. Is that true?

Any suggestions?

 

[Ken Slovak - [MVP - Outlook]]

Don't worry about it is my suggestion. I have about 20 different customized
versions of Redemption I use for various clients and my own private
development and what you see is normal. It won't happen on the user's
machine and if that custom Redemption is the only one installed they would
still need to use your custom names when using CreateObject to be able to
instantiate the Redemption objects. You will always see "Redemption" in the
Object Browser.