tag:blogger.com,1999:blog-9537945.post112182933930555880..comments2008-01-22T16:03:19.414-06:00Christopher Painterhttp://www.blogger.com/profile/12167478740431444267chrpai@yahoo.comBlogger1125tag:blogger.com,1999:blog-9537945.post-49578969098233526932008-01-22T16:03:00.000-06:002008-01-22T16:03:00.000-06:00When I originally wrote this article, I had never looked at capicom.dll and didn't know anything about it. I wrote the post on the assumption that the original poster had a valid reason for calling an Installer class. <BR/><BR/>In hine site, there was no valid reason. capicom.dll is an unmanaged automation object ( COM ) and in order to consume it in .NET you don't add it as a refernce, you generate a runtime callable wrapper using tlbimp and add the interop as a reference.<BR/><BR/>But InstallShield is unmanaged code so there is no reason to go to .NET in the first place. Just call the COM automation directory with CoCreateObject(). It also seems that CAPICOM.dll is built into windows these days so there is no reason to deploy it either.<BR/><BR/>So just google for CAPICOM SDK and download/install the MSI package. You'll find a samples directory including VBS which will give you everything you need to know to port this code over to InstallScript.Christopher Painterhttp://www.blogger.com/profile/12167478740431444267noreply@blogger.com