* "=?Utf-8?B?UmljaGFyZDUwNg==?=" <anonymous@discussions.microsoft.com> scripsit:
[quoted text, click to view] > I have been struggling for almost a year now, migrating my single VB 6
> client stand alone application to VB.Net. I have purchased six rather
> fat books on VB.Net, posted several questions on this board and finally
> purchased "Moving to VB.Net, Strategies, Concepts and Code" by Dan
> Appleman. He opened my eyes, because in the first three chapters, he
> made me realize that migrating to VB.Net is like putting a Pratt &
> Whitney jet engine into my family car. Also, the .Net Framework won't be
> in common use for a long while.
> So I have abandoned VB.Net and went back to easily upgrading my VB 6
> application inside VB 6. I say easily because of the stuff I have
> learned in my attempted migration. Microsoft has made VB.Net a
> beautiful, sensible coding machine with great debugging and great
> Intellisense currently with limited use.
ACK. It often doesn't make sense to "migrate" a VB6 project to .NET if
it is working properly and almost "finished".
[quoted text, click to view] > The result: I can now see all the coding, debugging shortcomings of VB
There are some big disadvantages in the current releases of VB.NET, like
the lack of edit & continue, etc. These things will be included in the
next release of VS.NET (2H 2004).
[quoted text, click to view] > 6. Wouldn't it be wonderful if Microsoft upgraded VB 6 to include all
> the features of code formatting and debugging that is in VB.Net???? They
> could call it VB 6-1/2 !!!!!!!!!!!!
>
> I won't hold my breath waiting.
It would be wonderful and it would make me happy too. There will be at
least a SP6 soon, but if won't include any enhancements of the IDE and
language.
--
Herfried K. Wagner [MVP]
