Vb.net

[CyberInfantry]

I've really only messed with VB 6.0, but I'm interested in moving up to .NET. For whatever reason I've been resisting the change, though.

Can I get your opinions on VB.NET and the .NET framework?

[Asgorath]

You should have moved to vb.net a long time ago

[Shaggy Hiker]

I spent years in VB6, and loved it. I also resisted moving to .NET because it was sufficiently different that the move was not totally painless. Eventually, however, I moved to take advantage of the Compact Framework. Once comfortable with that, I switched to using the language for everything else, and once I did, I lost all interest in ever using VB6 again. You can find the exact date by looking at my posts in the ClassicVB forum. I posted a fair amount in there, but after writing my first app in .NET, I believe that I never posted there again.

You might find it to be the same with you. VB6 just became aggravating because of the improved IDE in .NET.

[Pasvorto]

I am in the process of making the move. Each application I port to VB2005 presents a new challenge. I took the easisest ones first. I think it will be OK once I get everything ported and have no need to VB6 anymore.

[CyberInfantry]

One thing that has bothered me about the idea of switching is its reliance on the .NET framework. It just doesn't seem to me that it is that widespread yet. Java VM is everywhere. .NET is supposed to be like that, yes? Is Windows not the only OS that has a .NET framework?


If crossplatform capability is something added, the what does .NET have to offer that 6.0 doesn't?

Does it really make anything easier? Is it any more powerful?

[Shaggy Hiker]

There are a few added things, such as true OO support, which can make writing programs easier. It won't be faster in general, but it is fast enough. Many individual things are better/easier, though they tend to be small, specific things, like the Random class in place of Rnd and Randomize. However, the goal was crossplatform capability, which is something that may become common. Overall, .NET is a bit too new still to be everywhere yet.

Keep in mind that VB6 also had a necessary component in the VB Virtual Machine. Once it became part of the OS, people kind of took it for granted, but it always had to be there, and could be pretty big. The .NET framework is the same kind of requirement, it just hasn't ended up on all systems, and is so much larger than the virtual machine that it really jumps out at people.

[stanav]

Windows Vista has the .Net framework installed as default.... So once Vista is realeased and becomes popular as XP now, the requirement to run install .Net won't be a problem any more...

[techgnome]

You should have moved to vb.net a long time ago

And yet when you have close to a million lines of code in an app, it isn't easy to move to .NET.

One thing that has bothered me about the idea of switching is its reliance on the .NET framework. It just doesn't seem to me that it is that widespread yet. Java VM is everywhere.

It is NOW.... wasn't always the case.... it just takes time.

.NET is supposed to be like that, yes? Is Windows not the only OS that has a .NET framework?

No, there are Linux ports for .NET as well....

If crossplatform capability is something added, the what does .NET have to offer that 6.0 doesn't?

Does it really make anything easier? Is it any more powerful?

Truer Object Oriented Programming/Design. It's much more powerful in what it can do, things have been added to the language, while other things have been downplayed (I'm not aware of any actual removals)


-tg

[CyberInfantry]

Is VB.NET able to do polymorphism, recursion, and overloading the way VB 6 wasn't?


If I were to switch over to the dark side, should I go with Visual Studio 2005? I can get an academic version for US$57.00

[techgnome]

Yes, yes, and yes.

Before you spend a lot (or any kind of $$) ... get the Visual Basic Express edition from MSDN.... it's free, and you can upgrade it later. I don't know what kind of limitations the academic one has.

-tg

[CyberInfantry]

It has been my experience with all previous version of Visual Studio that the Academic version is the full professional version, just with an academic license.

I went ahead and ordered it from my college... Should have it in 3 days. :P

[CyberInfantry]

I just downloaded Express to play with until my Visual Studio gets in...

Where's a good place to start learning how to cross over from 6.0 to .NET 2005?

[jmcilhinney]

There's a link to an eBook in my sig aimed at just that, but any VB.NET tutorials are worthwhile. You should also make copious use of the MSDN library, which you no doubt installed with VB Express.

[CyberInfantry]

Okay, i'm checking out some of these "Learn .NET" sites... and omfg...

I feel retarded for resisting .NET for all this time! it is SO much easier and quicker (so far)!

[CyberInfantry]

Okay, my copy of Visual Studio 2005 Academic Standard edition just arrived. I was hoping I was purchasing the academic professional edition, guess I was wrong.

Anyway, what are the restrictions on the Express version? Are you allowed to produce software with it or no?

I know you cannot with the Academic version. It is soley for educational purposes.

What are the differences between VB 2005 Express and VB 2005 Standard?

[jmcilhinney]

You can compare the different versions of VS at MSDN. There are no limitations as far as what you're ALLOWED to produce using the Express editions but they do not have as many features. Examples of what's missing are Crystal Reports, Windows Installer distribution, Mobile development, etc. No self-respecting professional developer could last long with just the Express editions, but they are a great free tool for their intended market: students and enthusiasts.