Win32 to .Net DLLs, character sets
Managed C++/CLI
1
Posts
1
Posters
0
Views
1
Watching
-
Some questions on Win32/.Net interaction DLLs: When compiling a managed DLL that uses Win32 funcs, what character set should be selected, or does it always become unicode due to /clr? If one creates a native DLL that is to be used with [DllImport...] from .Net, what character set should be used there? I've seen them set to compile with MBCS. Is there a point in this? I know if it was set to Unicode it wouldn't work on W98, but does MBCS enable it to receive "exotic" unicode glyphs (they translate) from a .Net client app, or might it just as well be set to "Not Set"?