I think these resources might help - I'm thinking you would want to "attack" the system piecemeal...
Using Unmanaged (VB6) Code in .NET[
^]
M$ excerpt[
^] (NB this is a PDF download)
Other thoughts...
You could always run the executables using Process.Start but I'd be wary of how they might be doing cross-communication (hopefully it's all through the database). We did experiment with
named pipes[
^] for this and I think eventually used
memory mapped files[
^]. I left before the whole lot got converted so I don't know what they finished up which after the VB6 had gone.
Shame about the UserDocuments - not many people went down that route, but I would agree to converting them.
Beware - Don't assume that VB.NET is the obvious choice for converting from VB6 just because of the "similarities" - I would personally go for C# (although I suspect you don't have much choice in the matter)
Quote:
let's talk about grids
Nooooooo!
We had no end of bother with grids as there had been heavy use of custom and 3rd party controls. My oppo ended up writing a editable grid-control with variable height rows that could have fore- and back colours configured in C that we took forward, just to keep the UI looking the same(ish).