I slightly changed the subject of the thread and made this a sticky. We will keep it near the top for a little while to help anyone that is migrating over..
I suppose I can contribute to this thread since I am doing a 40,000 line VB6 conversion to .NET. I (highly) recommend biting the bullet and just doing a rewrite. There have been some good things about converting (like not having to rewrite some code), but in the long run...my feeling is that a full rewrite would have been better.
i thought it might be useful for anyone moving from vb6 to .NET or anyone who wants to learn about the basics of .NET
I think it was you who recently posted a link to SharpDevelop. As I currently can't afford the bucks or euros to go for .net I thought your suggestion was an interesting one. Now my question is, is the language syntax of .net the same as that of SharpDevelop, or will I have to start from scratch whenever I get .net even if I have acquired a basic yet fairly acceptable knowledge of SD?
Lottery is a tax on people who are bad at maths
If only mosquitoes sucked fat instead of blood...
To do is to be (Descartes). To be is to do (Sartre). To be do be do (Sinatra)
also you can download the .net 2005 beta for free and use that until you have a good grasp of the language and then upgrade to a pay version of 2005 (which would be out by then)
SharpDevelop is just another IDE for developing software in .NET, like visual studio. so there would be no differences to the actual code/syntax.
you could even code in notepad if you were feeling really hardcore...
Great. Now, what are the features I am exactly missing from .net? I mean, going from VB6 to SharpDevelop, would that be a step down?
Lottery is a tax on people who are bad at maths
If only mosquitoes sucked fat instead of blood...
To do is to be (Descartes). To be is to do (Sartre). To be do be do (Sinatra)
Option Strict On ' Requires Explicit Type Conversions eg. CType, DirectCast, ect.
Option Explicit On ' Requires Explicit Typing, Dim x as String, NEVER leave this off...
I tried SharpDevelop and found it lacking quite a few features.
It does use the .net framework syntx... so going from SD to .NET codewise won't be a problem.
But SD has no debugger.
Doesn't handle OCX or 3rd party .NET controls very well.
Doesn't do mobile very well
and no ASP controls or window forms.
Is only on version 1.0.3.
Although it is a good start for beginners.... if you are serious about using .NET, then get VS 2003 or 2005 (when it comes out)
If you are a student, you can get Academic for under a $100...
and no ASP controls or window forms.
The Windows forms controls are in the .Net Framework System.Windows.Forms
The asp.net controls are in the .Net Framework System.Web.UI
Is only on version 1.0.3.
There have only been two versions of Visual Studio .Net (and this does not much meaning anyway)
Although the ASP is in the framework... SD (SharpeDevelop) has not implemented them to use on the WinForms.... meaning that when you put code on the form it doesn't automatically write the needed code. They only have auto code creation for C# and VB.
VS may be on it's second version, but is way..way far more advanced.
SD is missing alot of functions. Not to mention that is is unstable.
mendhak said it best concerning SD...
"Pro's... it's free....... Con's.... it's free."
You get what you pay for with SD. (oh which is nothing)
.
Last edited by epixelman; Apr 9th, 2005 at 05:15 AM.
Although the ASP is in the framework... SD (SharpeDevelop) has not implemented them to use on the WinForms.... meaning that when you put code on the form it doesn't automatically write the needed code. They only have auto code creation for C# and VB.
VS may be on it's second version, but is way..way far more advanced.
SD is missing alot of functions. Not to mention that is is unstable.
mendhak said it best concerning SD...
"Pro's... it's free....... Con's.... it's free."
You get what you pay for with SD. (oh which is nothing)
.
Just because it isnt automatically done for you doesnt mean it doesnt work. you should be able to copy and paste the code from an form created in visual studio .Net and it should look the same.
Can you run both Visual Studio.Net and VB.net 2005 (Beta) on the same machine without any problems. I'm thinking about doing more with VB.Net but don't want to break my present version while trying the Beta.
Can you run both Visual Studio.Net and VB.net 2005 (Beta) on the same machine without any problems. I'm thinking about doing more with VB.Net but don't want to break my present version while trying the Beta.
Thanks,
Michael
Yes, you can install all different versions along side eachother, which includes VB6, VB.NET 2002, 2003, and 2005 beta
I dont recommend installing a beta version along side of another production version since M$ is famous for making the
beta versions not upgradeable nor uninstallable.
If you have a test system available (one that you can reformat) I would highly suggest that you install the
beta version on it instead, unless you dont mind having to reformat your production system in order to perform
an upgrade.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum.
Rob, did you actually experience a problem uninstalling the beta 05? I have not tried to, but I don't see why it would be a problem. Both the 2.0 beta framework, and the 2005 beta IDE are listed in the add/remove program list. And I don't see why there should be any issues. 2005 is really just enhancements to the IDE and framework, which means the basic concepts for installing/uninstalling stem from 2003 (which in turn came from 2002) I would hope the install/uninstall should be pretty standard by now...
I had read that the 2002 and 2003 had these issues when they were in beta. I havent taken too much of a
look into the 2005 but I am just waiting for a RTM release before I install on my production system along side of
VB6 and 2003.
Has anyone tried uninstalling 2005 beta yet?
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum.
IS .NET the new version of VB6 ya, or is it design for different application mainly networking?
I would say that VB.Net is based on VB6, there are quite a few difference.
Networking has been completely restructured... No More Winsock control, you need to Use the System.Net.Sockets Classes. More complex but much more powerful.
I think what chris meant was is the ".NET" in VB.NET because it is designed for networking, etc...
the .NET actually I think is more based on the concept of having a framework to run managed code versus having much to do with the internet or networking. Yes VB.NET can interact with the internet and networks worlds better than VB6, but it does just about everything worlds better than VB6
Im gettimg the feeling you can't use both VB and VB.Net installed on the same disk/machine/pc.
I want to keep coding in VB6 but want to dabble with VB.Net to check it out. Will probably use VS .Net 2003. So what will stuff up first and what is the work around?
Im gettimg the feeling you can't use both VB and VB.Net installed on the same disk/machine/pc.
I want to keep coding in VB6 but want to dabble with VB.Net to check it out. Will probably use VS .Net 2003. So what will stuff up first and what is the work around?
Are you sure man? I have the disks and Im about to install on your advice..... I remember something to do with global OS environment variables and compilation and execution problems.......
If you are wrong I'm sending you the grumpiest smiley I can find.
The only time there was any problems with VB6 and VS.NET on the same machine was when VS2000 was still in beta. Since it's gone gold, it hasn't been an issue. We've got VB6 and VS.NET 2003 here on everyone's machines and narry a problem. I do knwo that it's recommended that VB6 be installed FIRST, then .NET installed second.
I'm sure it will be fine. I felt the same when I first did a side-by-side install of VS6 and VS.NET 2003.
I have not had one issue yet after almost a year.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum.
No longer a .Net virgin I feel my inocense has been stripped away.
Looks very good! I compiled and packaged some of my VB6 Apps to check what would happen and all is ok. I can't seem to find the Deployment Wizard for VB.Net does it have one?
No longer a .Net virgin I feel my inocense has been stripped away.
Looks very good! I compiled and packaged some of my VB6 Apps to check what would happen and all is ok. I can't seem to find the Deployment Wizard for VB.Net does it have one?
Setup wizard is now a project.
So you may find it in the new Projet windows
I did actually. I uninstalled the .NET 2.0 beta framework and the IDE completely
Working fine I even installed the .NET 1.1 framework and VS.NET 2003 after that so I would say it works well.
I think this is only in the beta of 2005 but I couldn't compile right It never produced a .exe and there was always this weird installation thing that I didnt like.
Chicago, IL or St. Louis, MO (depending if I'm at school or not)
Posts
9
Re: Tips for moving from VB6 to VB.NET
I'm working on a program that I was originally doing in VB editor because I wanted to get a start on it while I waited for my VB2003.Net to come. I would like to somehow transfer this work from editor to .Net. Is there a way to do this? I have Window2000 Professional if that helps to understand what kind of editor I was using. I appreciate the help! Thanks!
Reply With Quote
Originally Posted by epixelman
installed on the same disk/machine/pc.
It never produced a .exe and there was always this weird installation thing that I didnt like.
