Re: Conversion from VB 6 to VB.NET 2005

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Vince (sdsad_at_fsd.com)
Date: 10/12/04 

Date: Tue, 12 Oct 2004 09:12:26 +0800

Thanks a lot everybody for the info. I'll invest some 4 days more in testing
and reading through the links. If it turns out to be Mission Impossible,
I'll develop the next version in .NET.
Vince
"Steve Long" <Steve_Noneya@NoSpam.com> wrote in message
news:%23xNfjW%23rEHA.896@TK2MSFTNGP12.phx.gbl...
> Good info Jay. Thanks.
> Steve
>
> "Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP@msn.com> wrote in message
> news:uiWrlw8rEHA.1816@TK2MSFTNGP09.phx.gbl...
> > Steve,
> > > Designing .NET test harnesses for your larger DLL's can be time
> consuming
> > > which begs the question: do I really need to do this.
> >
> > Absolutely!!! Especially when you write the tests first, then the code.
> > Which is the methodology behind TDD (Test Driven Development). NOTE:
With
> > TDD you do not write a "test harness" per se, you use an existing "test
> > harness" such as NUnit or csUnit, you do however write a suite of tests
> > (simply methods with asserts in them) that test your classes & all the
> > methods.
> >
> > I'm using NUnit 2.2 http://www.nunit.org/ and like it better then
earlier
> > versions (of NUnit). VS.NET 2005 Team System will have a TDD tool
built-in
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvsent/html/vsts-test.asp.
> >
> > I've been using TDD more and more over the last year or so. I find
Daniel
> > Cazzulino's comment to be my findings also:
> > http://weblogs.asp.net/cazzu/archive/2004/10/07/239449.aspx
> >
> > I recently starting reading James W. Newkirk & Alexei A. Vorontsov's
book
> > "Test-Driven Development in Microsoft .NET" which explains TDD in the
> > context of .NET, I would highly recommend this book!
> >
> > Of course if you don't have the tests to begin with, then you may have
> your
> > work cut out for you...
> >
> > NOTE: I would not migrate a VB6 project to .NET simply to be on .NET, I
> > would migrate the project so that I can leverage the full OO that .NET
has
> > to offer. I have a couple of substantial (100s of classes) projects that
I
> > have migrated. I find using Refactoring (http://www.refactoring.com) on
> the
> > migrated project to be an "easier" method of redesigning the app, rather
> > then design a brand new project in VB.NET...
> >
> > Hope this helps
> > Jay
> >
> > "Steve Long" <Steve_Noneya@NoSpam.com> wrote in message
> > news:OGa%23Ab8rEHA.896@TK2MSFTNGP12.phx.gbl...
> > >I just completed converting a project to .NET 2003 that was a large
> project
> > > and let me tell you, it is no trivial undertaking. If I had it to do
> over
> > > again, I would leave it and try to design a new project along the
lines
> of
> > > "little at a time" variety.
> > >
> > > The problem with writing your new DLL's in .net and making them COM
> > > compatible, is that it is difficult to debug between the two platforms
> > > (vb6
> > > and .NET). .NET doesn't do this very well were the projects are very
> > > large.
> > > This methodology is okay for smaller DLL's were you can test them
fully
> in
> > > a
> > > .NET test harness before moving them over to VB6 but is totally
> cumbersome
> > > for larger DLL's.
> > > Designing .NET test harnesses for your larger DLL's can be time
> consuming
> > > which begs the question: do I really need to do this. If not, leave it
> and
> > > let that VB6 code hang around as long as it is useful.
> > > Along with porting this app to .NET, I also ported the ActiveX DLL's
so
> at
> > > least now, I've got a bunch of .NET asymblies that are useful.
However,
> > > there was more than one time that I thought the whole project would
> fail.
> > >
> > > As for all those error messages that you get from the compiler, I just
> had
> > > to walk my way through them fixing them one at a time. There were some
> > > that
> > > didn't even really need fixing but the converter thought there was a
> > > problem. Nothing like doing a little desk checking I suppose huh?
> > >
> > > Steve
> > >
> > > "Chris Dunaway" <"dunawayc[[at]_lunchmeat_sbcglobal[dot]]net"> wrote
in
> > > message news:tm48g1s4uhtm$.z0c92nhkzpbk.dlg@40tude.net...
> > >> On Mon, 11 Oct 2004 14:13:05 +0800, Vince wrote:
> > >>
> > >> > I am trying to convert a VB 6 application to VB.NET 2005 using the
> > > wizard.
> > >> > It has over 20 forms and I've used Option Explicit everywhere,
hence
> > >>
> > >> Since your VB6 project is more than 20 forms, I presume that it is a
> > >> large
> > >> application. Even if the conversion wizard completed without any
> errors,
> > >> it is likely that the result would be less than optimal.
> > >>
> > >> Is it absolutely necessary that the app be converted to .Net? If
not,
> I
> > >> would recommend keeping the app in VB6 and then begin to convert or
> > >> redesign the next version of the app to fit the VB.Net design
paradigm.
> > >>
> > >> --
> > >> Chris
> > >>
> > >> dunawayc[AT]sbcglobal_lunchmeat_[DOT]net
> > >>
> > >> To send me an E-mail, remove the "[", "]", underscores ,lunchmeat,
and
> > >> replace certain words in my E-Mail address.
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: XP: Cool feature with a weakness
    ... no, Steve, I have no desire to go point by point with your trolling. ... I repeat: ... and let go of that all consuming ... Macs are Macs and Apple is still making and selling Macs ...
    (comp.sys.mac.advocacy)
  • Re: is svchost.exe a virus?
    ... System Idle Proccess, is consuming 97 cpu, every thing else is cero. ... "Steve N." ...
    (microsoft.public.windowsxp.general)