K
Katit
Hello,
I searched archives and all pointing to use of VB6 objects from C#
I want something different.
1. How can I build expandable platform? Let's say DLL's will have
common set of methods (interface) and I will have main program using
those DLL's. I want to achieve when I won't have to recompile main
program and be able to add modules by dropping them into folder. Then
my main program will know about them from DB.
2. I want something like ActiveX.exe to execute those "plugins" in
their own threads. And it will be ideal if main app won't crash in case
one of the DLL's have bad code. We want DLL's to execute code in it's
own memory space.
Can you give me kewords, pointers on where/what to read on this topic?
TIA!
I searched archives and all pointing to use of VB6 objects from C#
I want something different.
1. How can I build expandable platform? Let's say DLL's will have
common set of methods (interface) and I will have main program using
those DLL's. I want to achieve when I won't have to recompile main
program and be able to add modules by dropping them into folder. Then
my main program will know about them from DB.
2. I want something like ActiveX.exe to execute those "plugins" in
their own threads. And it will be ideal if main app won't crash in case
one of the DLL's have bad code. We want DLL's to execute code in it's
own memory space.
Can you give me kewords, pointers on where/what to read on this topic?
TIA!