views:

343

answers:

1

This is my set up

  1. C# application - Sample.exe

  2. C# control exposed for com which hosts the C# application

  3. PowerBuilder instantiates C# control

  4. PowerBuilder destroys C# control which in turn gets to the Dispose method of the c# control

  5. The dispose method uses Process class to destroy the C# application or it should. This is where I have an issue. The C# application is still running when I look in task manager.

  6. When i close my POwerBuilder application, my c# application no longer appears in TaskManager which makes me to believe that my PowerBuilder app still is holding on to a reference of my C# control.

any ideas on how i can avoid situation 5?

A: 

I don't understand why you need a C# executable when a regular COM dll (in C#) would do.

Otávio Décio
I have an old legacy c# application which needs to be hosted within PowerBuilder with some other features. yes it is a weird architecture that cant be avoided atleast not with VS-2005. Tried to get all parties to go with VS-2008 and use the add-in framework