Thanks Brad.... > 1) Use P/Invoke in Visual Basic.NET and call the functions in the DLL
>This should certainly work, and is the path of least resistance, especially >since I'm assuming that the DLL currently just exports a bunch of functions >(since you couldn't have directly consumed a C++ class from VB4). Yes the DLL just exports a bunch of functions to VB.. > 2) Recompile the C++ DLL using IJW switch so that it will be a managed one. > Compiling with /CLR doesn't buy you anything until you have managed classes > wrapping the existing C++ classes and/or functions. This is more work, but > depending on your needs, may also offer more flexibility (because you get to > move things into objects that can not only be created, but extended). I still don't understand what the advantage IJW gives to the programmer(if we have more work to do). So if we compiled with IJW, we write another managed wrapper and use that with languages like VB.NET or C#. Its a two step process to use in a managed application written using VB.NET or C# If my assumptions are wrong, please correct me... Thanks in advance, Madhu You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
