Neither VB6 nor VB.NET can make normal DLLs. They are ActiveX controls which are a totally different and rather more complex beast.
Not entirely true Robert. As for VB6 the dll's created actually are COM compontents (which AcitveX controls are a subset of) that interacts with other applications using a COM intreface/COM interop.
And as for .NET, Microsoft has actually dropped the term ActiveX, since the introtuction of the .NET framework. Whatever language you use everything will be parsed to IL and CRL, so it makes more sense to speak about managed an unmanaged code. So you could say that VB.NET cant create unmanaged code (but as we've seen, it can!) but that doesn't really make the resulting DLL an ActiveX control.
Sweenie - Ok i thought you were calling a VB6 dll from blitz. BTW have you done any tests with C#? As I said I've done some and everything has worked fine. Have you tried doing a call from VB6 to an unmanaged (By IL manipulating) C#.NET dll? If you can do that I guess that it's safe to say that some other components of the IL need tweaking in the case of VB.NET code.
I could send you my VB.NET dll if you'd like. As I have mentioned it does not work all the way. But at least it does not shut down blitz. The only thing that does not work is the input parameters. It returns data to blitz quite happily. It would be interesting to see if you can run it.
//PetBom