VB6 to .NET

  • Thread starter Thread starter Giacomo
  • Start date Start date
G

Giacomo

I updated a project that has everything late bound (Sqldmo and scripting
runtime). It works in VB6, came across fine in the upgrade process,
compiled.... sounds great so far hmmm? It works fine when I test it on
another machine with the .NET loaded on it. I tried it on a machine that
doesn't have .NET installed, but the Framework is and it fails immediately
with

Application has generated an exception that could not be handled

I'm not sure what to make of this. This is actually the program I wrote to
update the MSDE (it detaches a database that is corrupt and reattaches an
older, non corrupt database in a worst case scenario).

Do I need to write an installation program for this installation tool I've
written to work? (which is what I use this program for). I, probably
mistakenly, am assuming I can distribute .NET objects which run platform
independent provided Framework is installed.

If I were to guess, I would say the answer is, of course you need a setup
program to distribute an object, which is contrary. Why did I bother to
write an object that uses late binding to run a data detach on my MSDE
distribution if it needs an early bound object installation?

HELP me figure out why this happens this way.

Thanks,
 
Hi ,
Well you just need the .Net framework installed on a target machine for it
to run. But you have converted a project from VB 6.0 to .Net. If the VB6
app is using VB6 controls and VB6 references, then during the upgrade
processs, the wizard generates wrappers to the VB6 components. You might
hvae to deploy these components on the target machine. The other thing I
can see happening is, in the two machines where you tested your app and it
works, it might have all the components required by your project and the
third system might not have it. So using .Net you can create a setup
package and deploy it on your target machine.

Thanks



Anand Balasubramanian
Microsoft, Visual Basic .NET

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks
 
Back
Top