6 .net, 2008

[sgrya1]

I started using vb6 years ago and is the only programming software that I have.

Visual Basic 2008 express seems to be free but haven't looked at it yet.
Is there a full version of VB 2008?

There's .net but I have no idea on what the difference is there.

Can anyone elaborate on the pros and cons of each?

[RobDog888]

VB 2008 Express is the light free version of VB 2008. VB 2008 is not free and has several versions. .NET is just the framework/engine which VB/C# are built/based upon. Think of how VB6 has runtime dependancy files like msvbvmm60.dll and its other ocx's and VB 2002-2010 runtime dependancies as the .NET Framework.

For the pro's and con's try a search here on the forums because over the years we have accumulated many threads on the topic

[sgrya1]

Thanks again Robdog, I did try a couple of searches but maybe haven't found the right keywords yet.

.Net was moved up in the rankings years ago on vbforums. Is VB6 considered old hat now or is it still much the same?

[sgrya1]

I suppose what I'm really asking is should I get with the times?

I only really dabble with VB6 apps but some things are an abolute headache. I still have issues with some of my apps. Just wondering if issues are being sorted out with .net leaving vb6 problems to those who are willing to carry on with it.

[si_the_geek]

VB6 is very old (released in 1998) and unsupported (VB6 apps should work on Windows 7, but probably not on later versions).

The amount of people using it is going down steadily, and for a while we have had more activity in the VB.Net forum than the VB6 forum - hence the position change. There are still several of us helping, but that will presumably reduce over time.

Some things are dramatically easier in .Net (such as menu icons, form resizing, etc), so after a bit of practice with it you will be more productive.

[MartinLiss]

My NumberBox control which is written in VB6 is used by a bunch of people including sgrya1. I don't really know anything about .Net programming so would I be taking on too much if I were to try to convert it as my first .Net project? If I decided to try, what specific software would I need to buy or download?

[vb5prgrmr]

Not having played with that control, I would think 2k8 Pro should do (I have 2k2, 2k3, (I think some where I may even have 2k5) and 2k8 pro) all studio (not just vb.net) so my suggestion is to get the studio pro version...

See this link to compare...

http://www.microsoft.com/visualstudi...y/default.mspx

If you just want VB...

http://www.microsoft.com/express/download/


However, if you are a book guy like I am, there are books out there with both VB.NET and C#.NET examples side by side for comparisons so you can use/learn both at same time if you get the studio.


Good Luck

[Joacim Andersson]

My NumberBox control which is written in VB6 is used by a bunch of people including sgrya1. I don't really know anything about .Net programming so would I be taking on too much if I were to try to convert it as my first .Net project? If I decided to try, what specific software would I need to buy or download?

Hi Marty, converting one of your project is an excellent idea that could get you a jump start into the wonderful world of .Net. As an MVP you should have got a complimentary MSDN subscription and is allowed to download Visual Studio Team System 2008 for free.

[MartinLiss]

Hi Marty, converting one of your project is an excellent idea that could get you a jump start into the wonderful world of .Net. As an MVP you should have got a complimentary MSDN subscription and is allowed to download Visual Studio Team System 2008 for free.

Oh, yeah, I forgot about that.

[sgrya1]

Martin,

Your numberbox control works in .net.

I only just worked out how to add it. Right clicking in the toolbox area and selecting choose items. It is listed in the COM Components

[MartinLiss]

Martin,

Your numberbox control works in .net.

I only just worked out how to add it. Right clicking in the toolbox area and selecting choose items. It is listed in the COM Components

Great!

[Joacim Andersson]

The only problem is that the .Net framework has to go through the COM interop thing which is a rather slow process. Of course there is no real need for the conversion other than what Marty might learn during the process.