Galen Somerville said:
Naw, it's too late for that. already went through 100's of errors and
warnings during the conversion. And I can only test a little of the
program
But... but.... this would be the UI only. Just grab the old VB6 form, open
it in VB6, rip out all of the code, leaving the controls in place, run the
utility, convert this "UI Only" form to dotNet, open it and your current
project in separate instances of VS, copy all controls from the converted
form to the clipboard, select the new project, select all controls on the
form, hit the delete key, hit Ctrl-V to paste.... that should be it.
startup as it works with a USB proprietary device. The beta version of the
USB interface has problems which hopefully will be solved this week.
I was thinking of writing a VB6 program to go through the .vb files and
changing by 1.28 but then I would have to study the makeup of the .vb
files.
Well... if interested in my "quicky" wizard, here ya' go...
http://www.vbsight.com/zips/Resize_Form_File.zip
There's not much to it and it won't alter the original unless you want it
to. Note that there's no font scaling because I couldn't find a decent way
of finding exact font sizes (scaled TT fonts show jagged edges if not sized
to one of their "natural" sizes)
And in VB6, if I make one mistake, it causes no end of problems. If you
have read my other posts you would know that an unhandled VB6 exception
brings up the VB2005 debugger and I end up back at the desktop.
GalenS
An unhandled exception that goes from VB6 to dotNet?... of course, any
unhandled exceptions in VB6 will kill the app. It's always been that way.
fwiw, dotNet in general "causes no end of problems" here. The simplest of
samples fail to run. I gave up completely for now. Waiting until I have a
chance to wipe my drive and start from scratch (how's that for "user
experience" eh? <g>)... fwiw, I selected the option to notify MS of my usage
data, etc (can't recall the name of the option)... if they're checking my
logs, they'll see that every time I try anything at all, there's a crash and
burn involved so.... For now, I'll stick with my "Rock Solid and Blazing
Fast" VB6. Plus, the only thing better than VB6 help is VB5 help. The newer
MSDNs are nearly impossible to use (very slow/very
bloated/crash-hang-o-matic) and when/if you find what you're looking for,
the "help" is usually useless.