Hi all,
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
variables are properly declared and used. I also made sure that there was no
design time (ItemData) listings in the list. However, when I try to convert
to .NET, two things happen:
a) It gives me over 5500 errors!! (Many of them include 'could not resolve
type' inspite of explicit declarations)
b) It quits halfway with a message like "An exception has occurred". The
usual Report to MS crops up and at the end of it, I am left with over 5500
baffling errors and a failed attempt at conversion.
My questions are:
a) Is there anything I can do in the existing VB 6 program to ease the
conversion process?
b) Any sites on the web that provide a lot of information on this?
c) Does anybody know why the thing quit halfway through the conversion?
d) This is a live project that I developed an year back and is likely to be
used for a long time to come. Is it necessary that I take the pains to learn
and shift the application to .NET?
If I need to send the report (over 2 MB!!!) please let me know.
Would appreciate any insight into this.
Vince
9  1433 
"Vince" <sd***@fsd.com> schrieb im: I am trying to convert a VB 6 application to VB.NET
2005 using the wizard.
Notice that this is still Beta software!
a) Is there anything I can do in the existing VB 6 program to
ease the conversion process?
Micrososoft Visual Basic Code Advisor
<URL:http://msdn.microsoft.com/library/en-us/dnvb600/html/vb6_FixItRuleTool.asp>
b) Any sites on the web that provide a lot of information on this?
<URL:http://msdn.microsoft.com/vbasic/using/migrating/>
d) This is a live project that I developed an year back and
is likely to be used for a long time to come. Is it necessary
that I take the pains to learn and shift the application to .NET?
If the project is split up into multiple components, you can start
converting some of the DLLs, make them usable from COM and use then instead
of the ActiveX DLLs.
--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
Vince,
VBNet 2005 does not exist
VBNet 2005 Beta exist, so you showed that the conversion is not yet what it
maybe would be.
A very good newsgroup for discussions about that is http://communities.microsoft.com/new...idbey&slcid=us
Just my 2 eurocents
Cor
"Vince" <sd***@fsd.com> Hi all,
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
variables are properly declared and used. I also made sure that there was
no
design time (ItemData) listings in the list. However, when I try to
convert
to .NET, two things happen:
a) It gives me over 5500 errors!! (Many of them include 'could not resolve
type' inspite of explicit declarations)
b) It quits halfway with a message like "An exception has occurred". The
usual Report to MS crops up and at the end of it, I am left with over 5500
baffling errors and a failed attempt at conversion.
My questions are:
a) Is there anything I can do in the existing VB 6 program to ease the
conversion process?
b) Any sites on the web that provide a lot of information on this?
c) Does anybody know why the thing quit halfway through the conversion?
d) This is a live project that I developed an year back and is likely to
be
used for a long time to come. Is it necessary that I take the pains to
learn
and shift the application to .NET?
If I need to send the report (over 2 MB!!!) please let me know.
Would appreciate any insight into this.
Vince
Thanks for the links & info Cor & Herfried.
I wanted to migrate to VB.NET but since its new brother (2005) is in town,
it's hard for me to think 2003, although 2005 is still a beta.
Vince
"Cor Ligthert" <no************@planet.nl> wrote in message
news:uq**************@TK2MSFTNGP15.phx.gbl... Vince,
VBNet 2005 does not exist
VBNet 2005 Beta exist, so you showed that the conversion is not yet what
it maybe would be.
A very good newsgroup for discussions about that is
http://communities.microsoft.com/new...idbey&slcid=us
Just my 2 eurocents
Cor
"Vince" <sd***@fsd.com>
Hi all,
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
variables are properly declared and used. I also made sure that there
was no
design time (ItemData) listings in the list. However, when I try to
convert
to .NET, two things happen:
a) It gives me over 5500 errors!! (Many of them include 'could not
resolve type' inspite of explicit declarations)
b) It quits halfway with a message like "An exception has occurred". The
usual Report to MS crops up and at the end of it, I am left with over
5500 baffling errors and a failed attempt at conversion.
My questions are:
a) Is there anything I can do in the existing VB 6 program to ease the
conversion process?
b) Any sites on the web that provide a lot of information on this?
c) Does anybody know why the thing quit halfway through the conversion?
d) This is a live project that I developed an year back and is likely to
be
used for a long time to come. Is it necessary that I take the pains to
learn
and shift the application to .NET?
If I need to send the report (over 2 MB!!!) please let me know.
Would appreciate any insight into this.
Vince
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.
Hi Vince, it's hard for me to think 2003, although 2005 is still a beta.
Vince
It's a risky and extremely frustrating process developing software with
a beta IDE, rather you than me!
Nick.
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:tm****************************@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.
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/de.../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...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" <St**********@NoSpam.com> wrote in message
news:OG***************@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:tm****************************@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.
Good info Jay. Thanks.
Steve
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:ui**************@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/de.../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...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" <St**********@NoSpam.com> wrote in message
news:OG***************@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:tm****************************@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.
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" <St**********@NoSpam.com> wrote in message
news:%2*****************@TK2MSFTNGP12.phx.gbl... Good info Jay. Thanks.
Steve
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message
news:ui**************@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/de.../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...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" <St**********@NoSpam.com> wrote in message
news:OG***************@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:tm****************************@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.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: junky_fellow |
last post by:
Can anybody please explain this:
When a value with integer type is converted to another integer type
other than _Bool,
if the new type is unsigned, the value is converted by repeatedly...
|
by: Sanjay Kedare |
last post by:
Hi,
I am evaluating various alternatives of converting Delphi (Ver 4.0) screens
to C# screens. Are there any tools available for such conversion? if yes how
much conversion do they achieve? The...
|
by: Peter Oliphant |
last post by:
I've been trying all morning to convert my 2003 project (managed) to 2005
(/clr since I have both managed and unmanaged code). I'm guessing I have
tens of thousands of lines of code to change. Did...
|
by: rawCoder |
last post by:
Hi,
Just wanted to know if there is any speed difference between
VB conversion Keywords like CInt, Clng, CStr, CDbl, CBool etc.
..NETs Convert.To<...> methods.
And which is better to be...
|
by: musosdev |
last post by:
Hi
I've got a project I've just run through the conversion wizard, and it's
giving me a few headaches.
I've got a user control which has controls referrenced from its calling page...
|
by: Coleen |
last post by:
Hi All :-)
I'm new to this site. I've been trying to convert several .Net 2003 web applications and getting tons of conversion errors.
I found this site to help walk me through the...
|
by: Blasting Cap |
last post by:
I'm trying to convert a 1.1 app to 2.0, and keep finding one thing after
another that either Framework 2.0 or Visual Studio 2005 doesn't like.
Now this -
In the global.asax, code that has been...
|
by: Randy |
last post by:
I've converted a VS 2003 project to VS 2005. I have one utility class that
it put in the APP_CODE directory. When I try and compile I'm getting this
error...
Error 1 The type or namespace name...
|
by: Ivan Velev |
last post by:
Hello,
Minimal example below - it gives me different output if I comment /
uncomment the extra time.mktime call - note that this call is not
related in any way to main logic flow.
When...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
