VB6 DLL works great in VB6 but not in .Net

[Guest klabranche]

I wrote a network enumeration DLL using API calls like NetEnumServer ect... Everything works wonderfully in VB6. I wrapped up the functionality in a DLL and tried to create a .Net example using the COM DLL. Now I am getting an invalid parameter or Browser not available error when I call the method that uses the NetEnumServer API call. Everything is the same except for .Net. Otherwise, I am using the same computer, same DLL, and practically the exact same code to call this method in .Net as I did in VB6. The only difference in .Net is the syntax changes. Anybody have any idea why the NetEnumServer API would crash in VB.Net even when being called from a VB6 COM object?

 

Kevin

:confused:

[divil]

There could well be a .NET way of doing the same thing, check out the classes in System.Net.

[Guest klabranche]

System.Net won't do it and System.Management only works with Active Directory Enabled networks and WMI (To my knowledge)..... Our network is still mostly NT4 based so ADSI won't work and every attempt using WMI to do this for me has failed. Ofcourse, I have never messed with WMI API at all and the help on it has been horrible. I could very easily be missing it.....