Link to home
Start Free TrialLog in
Avatar of CASorter
CASorterFlag for United States of America

asked on

vb6 to vb.net conversion seems to have left something out

we recently did a fairly simple vb6 to vb.net conversion using the visual studio 2005 conversion tool.

the program has database accessing,  text box controls, some progress bars some IP access of devices...

we got everything running fine.  tested it on 3 different development machines.  all ok.


when we went to put it on a faily vanilla windows 7 pro 64-bit 8gig workstation
 
it crashed before it even got far enough to do any error handling.

after much head scratching and what not.  we realized the common link on the stations where it worked was that visual studio was loaded on them.

we loaded a complete install of visual studio 2005 on the machine that wasnt working...  

the program worked.

we uninstalled visual studio 2005

program crashed as before.

we narrowed it down to the visual basic component of the Language Tools.

if we install it.. it works, if we uninstall it.. it fails.

SO...

has anyone heard of any components that might get left out when compiling a converted program?

or

does anyone know what is added when the visual basic component of Visual studio  is added?

or

any idea why this might be happening?

TIA
ASKER CERTIFIED SOLUTION
Avatar of Nasir Razzaq
Nasir Razzaq
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of CASorter

ASKER

some guidelines concerning how to use the tool would have been nice.
It shows you a list of assemblies not found. Guidelines for configuring it were in the liked article. What was missing?