Deployed managed COM Add in does not start

M

Michael Cross

Hello NG,

I have problems with the deployment of managed COM add ins and
recongnized a strange behaviour. As I descibed in my preview posting,
I build a setup project for a small COM Add In written in VB .NET. If
I install this setup on my target computer, the COM add in will be
loaded at startup of the host machine. But my bigger project won't
start if I try to deploy it in the same way.

Therefore, I commented all the code (except the Extensibility2 and
some click events), build a setup project and installed it on the
target computer. The add in startet. Then I added the first object in
my code by uncommenting the appropriate line, build a setup project
and installed it again on the target machine. But after a few objects
I added again to my add in, the add in didn't start on the target
machine. What was happen? What kind of changes occured to the setup or
to the project that the com add in didn't start anymore?

The secruity settings are setted to their lowest level and the
registry entries are done by the setup.

Has anybody an idea or can give me a hint in this case? Has anybody
similiar experiences?

Any help will be greatly appreciated.

Kind regards,

Michael Cross
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top