Wrote some good stuff with that. Ported it to Windows 3.1.Did you know that Microsoft came out with "Visual Basic for DOS"?
It was a full event-driven UI that ran in DOS (text mode) and used the mouse to place/draw controls on "windows" - that even had shadows! (darker colored text underneath the right and bottom side to give the shadow effect).
It was the next generation of MS Basic Pro - I was a beta tester for it - code named "Esher"
And it looks like you can download a free copy from here:
I based my assessment on sample converted code I saw on a forum a long time ago when the issue first came up. My understanding is that the conversion only handles the most basic of Visual Basic functionality. Therefore the amount of customization will vary a lot depending on what kind of code you feed it. I should not have put a percent on that as obviously it will be project dependent.I'd have to disagree with this statement, as you say you have not done it! There are a lot of minor irritating issues to sort out in trying to convert a VB app to VB.NET!