importing dll into vb.net

[swight]

I am a vb.net programmer transitioning to using masm. I was wondering which calling convention I would need to use(if one exists) in a masm dll to be compatible with vb.net's "imports" statement that implicitly loads a dll rather than using a bunch of DLLImports or P/Invokes. If there are none is there any program that can auto-generate a wrapper for .net.

[zooba]

I don't think you'll find it possible to achieve what you want without using platform invokes. MASM DLLs tend not to include enough information (parameter types, usage, etc.) to be able to reliably auto-generate a wrapper.

Probably your only hope in this area is to create a COM DLL, for which VB can create a wrapper. This is, however, at least as much work as writing a VB wrapper manually.

Cheers,

Zooba :U