"Dave" <D***@discussions.microsoft.com> wrote in message
news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> Hello,
>
> I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> but most of my VB6 code is business logic, not GUI stuff.  I've found a
lot
> of commentary on VB6 vs VB.net GUI differences, but very little about the
> compatibility of the "logic code".
>
> Any thoughts, or can you point me to some specific resources about this?
>
> Thanks in advance - Dave
>

"Dave" <D***@discussions.microsoft.com> wrote in message news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> Hello,
>
> I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> but most of my VB6 code is business logic, not GUI stuff.  I've found a lot
> of commentary on VB6 vs VB.net GUI differences, but very little about the
> compatibility of the "logic code".
>
> Any thoughts, or can you point me to some specific resources about this?
>
> Thanks in advance - Dave
>

"Douglas Marquardt" wrote:

> Hi Dave:
>
> http://vb.mvps.org/vfred/breaks.asp
>
> Doug.
>
> "Dave" <D***@discussions.microsoft.com> wrote in message news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> > Hello,
> >
> > I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> > but most of my VB6 code is business logic, not GUI stuff.  I've found a lot
> > of commentary on VB6 vs VB.net GUI differences, but very little about the
> > compatibility of the "logic code".
> >
> > Any thoughts, or can you point me to some specific resources about this?
> >
> > Thanks in advance - Dave
> >
>
>
>

"Dave" <D***@discussions.microsoft.com> wrote in message
news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> Hello,
>
> I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> but most of my VB6 code is business logic, not GUI stuff.  I've found a
lot
> of commentary on VB6 vs VB.net GUI differences, but very little about the
> compatibility of the "logic code".
>
> Any thoughts, or can you point me to some specific resources about this?
>
> Thanks in advance - Dave
>
>

"Michael D. Ober" wrote:

> First, if you haven't already switched to VB.Net, don't bother with VB 2002
> or 2003 as the IDE and debugger are a significant step backwards from VB 6.
> Take a look at VB 2005 instead.
>
> Now to your question.  If your Business Logic code is well written, the VB 6
> to VB 2005 up compiler will help.  There will, however, be a lot of code
> that simply won't convert well.  What seems to work best is to rewrite the
> code in VB 2005 and use the VB 6 code converter tool to convert those pieces
> of code that use VB 6 specific features.  Using the code converter in this
> manner works - converting entire projects isn't worth the effort.  Also,
> there are a lot of features in the .NET 2.0 libraries that eliminate the
> need for much of the messiness of VB 6's collections and API interfaces.
>
> As for porting current applications - don't unless there is a resounding
> need to rewrite or extend them.  VB 6 and VB 2005 will happily coexist on
> both the development systems and client systems.
>
> Also, if your business logic is in the form of COM objects, VB 2005
> applications can access them directly via the COM interoperation subsystem
> in dotNet.
>
> Mike Ober.
>
>
> "Dave" <D***@discussions.microsoft.com> wrote in message
> news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> > Hello,
> >
> > I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> > but most of my VB6 code is business logic, not GUI stuff.  I've found a
> lot
> > of commentary on VB6 vs VB.net GUI differences, but very little about the
> > compatibility of the "logic code".
> >
> > Any thoughts, or can you point me to some specific resources about this?
> >
> > Thanks in advance - Dave
> >
> >
>
>
>
>

"Dave" <D***@discussions.microsoft.com> wrote in message
news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> Hello,
>
> I'm an experienced VB6 developer and new to VB.net.  Its kind of unusual,
> but most of my VB6 code is business logic, not GUI stuff.  I've found a
> lot
> of commentary on VB6 vs VB.net GUI differences, but very little about the
> compatibility of the "logic code".
>
> Any thoughts, or can you point me to some specific resources about this?
>
> Thanks in advance - Dave
>

"Bonj" <a@b.com> wrote in message
news:#Cz5AkvYFHA.3300@TK2MSFTNGP14.phx.gbl...
> the main difference you'll find is vb.net has a garbage collector,
> constructors and implementation inheritance, which gives the possibility
to
> cram a lot more logic into one line of code. e.g. creating an object,
> setting properties and calling a method on the new object probably needs
at
> least 3 lines of code in VB6, but one in vb.net, whether this is a good
> thing or a bad thing is debatable as it depends on your opinion of whether
a
> long line of vb.net code looks worse than a short line of vb.net code.
>
> "Dave" <D***@discussions.microsoft.com> wrote in message
> news:BE6F2B62-25C1-4FC7-A5FA-FF897E9A2722@microsoft.com...
> > Hello,
> >
> > I'm an experienced VB6 developer and new to VB.net.  Its kind of
unusual,
> > but most of my VB6 code is business logic, not GUI stuff.  I've found a
> > lot
> > of commentary on VB6 vs VB.net GUI differences, but very little about
the
> > compatibility of the "logic code".
> >
> > Any thoughts, or can you point me to some specific resources about this?
> >
> > Thanks in advance - Dave
> >
>
>