Thanks, we are also investigating if can provide a wrapper so native
c/c++ (such as VC++6.0) code can use .NET system libraries directly.
You can consider a .lib and some .h files for a .NET assembly, then
from unmanaged c/c++ code, you can use them directly.

Huihong

http://www.remotesoft.com/linker
Remotesoft

To the best of my knowledge, we are the only ones that do real native
compilation. All other approaches are just adding a native loader, and
wrap everyhing into a single exe with a schema similar to
self-extracting exe. Inside the exe, there are still pure .NET
assemblies with the original MSIL code. The startup is extremely slow,
and the performance is poor, compared to running when .NET Framework is
available. Since when you wrap CLR runtime and .NET assemblies into a
single EXE, ngen can not be used, so all of the execution, including
system libraries, must be compiled at runtime. In other words, prejit
advantage is lost with those approaches. Another big disadvantage is
that it does not provide protection against reverse engineering, since
the wrapped EXE can be cracked easily.

Our approach compiles everything into x86 code, so the resulting
application has the fastest startup time, with the best performance.

And since it's natively compiled, it naturally provides the best
protection against reverse engineering. Native code is still the best
protection today.

Huihong
Remotesoft
http://www.remotesoft.com/linker/