>>I read once, somewhere, an article about Managed C++ which explains to how
>expose some unmanaged function pointer from your managed DLL.
Hence maybe you can write a MC++ wrapper of your C# applet and expose a
CplApplet() function.
I'd like to know more about this.
Some googling later:
http://www.codeproject.com/KB/dotnet/bridge.aspx
quite simple, isn't it?
>However there is a potential problem, maybe that's why many OS cmponent
can
be develop in managed language: You can have 1.x and 2.x and up applet in
the same process, otherwise you'll get some, hu.. problem I can't
remember
of...
Pardon me? I don't quite understand what you're saying.
Well, simply put, the (.NET 1.x) and (.NET 2.x (and 3.x)) are mutually
exclusive and causing each other to crash.
As explain by Jess Kaplan here:
http://forums.msdn.microsoft.com/en-...-8e962124043e/
Therefore the problem is following: you might want to write a shelll
extension in .NET2, but then any other application on your PC which use a
different runtime will crash while doing things such as opening a file
dialog.
(there is only 2 runtime 1.x and 2.x and up, all .NET framework 2.x and up
all use the same runtime, just different library)
mmh... not sure if it is really your problem though...
ho well, I refreshed my memory!