...Can this be done?

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"?

what he wants do to is probably the same as i; getting members a la IntelliSense...

Whenever I edit a longer string prop in the properties box, I get a tooltip showing the whole value of it (quite quickly) that seems to prevent setting focus to the actual feeld, so while the cursor blinks inside it, pressing keys hits the selected form control rather than the the string, so delete won't delete a character, it deletes a button or something... I've tried the codeproject killtt, but it kills every tooltip BUT this one...