Visual Basic .net or C+/++ .net or C# .net?

  Gaz 25 23:23 24 Jan 05

Or, stay with my Visual Basic 6 learning edition, which I must say I am finding limitations with.

If I use .net framework enabled Visual Basic development suites mean that all the customers who use my software would have to install .net?

If so, this is troublesome because not everyone has .net installed. Thus, I might as well begin learning Delphi 7/8?

I have delphi installed, but it seemed a little buggy for my liking, to be completly honest, although delphi is good - it needs a bit of work, especially for ease of use. Though claimed to be simple, I find it somewhat confusing at times, Visual basic to me seems easier.

Any ideas?

  Rigga 09:05 25 Jan 05

Well here's my two peneth.

Your fears over using .NET to write programs then not having customers to sell those programs to, is fairly unfounded. .NET is here to stay, and the .NET framework is included in SP2 I believe, (Not 100% sure because I've had .NET framework installed since the beta!).

Either way as more and more programs are released that use the framework, then there will be less and less Windows OS's out there without the framework installed.

The only real limitation to using .NET is that it is not available for Linux. Although I believe that people are working on an open source alternative, to get .NET programs to run. But from a commercial point of view unless there is a major shift in the OS market, then .NET on Windows OS will be a viable platform for years to come!.

As for the different .NET languages, well it's really down to taste, and what you are comfortable with. I personally use VB.NET which is mainly down to the Visual Studio editor being more friendly when using VB than when using C#.

The main difference with any of the .NET languages is just semantic, as they all use the same underlying Object Oriented structure. And I have yet to find something that I cannot do in VB.NET but can do in C#.

Plus moving from VB.NET to C# or the other way around is fairly painless. The only thing I would say for C# is that it is more semantically (is that a word!) similar to Java than VB is. So if you wish to move toward a JAVA environment at some point then maybe C# is the way to go.

The biggest change from a VB6 to .NET environment is the Object Orientation. Which you will need to understand fully to make the most out of the .NET languages. (VB6 does support OO to a degree, but it is not a full OO language!).

If you are fairly conversant with VB6, which if you are finding limitations then I'd guess you are, then the smallest leap is to VB.NET. If you then wish to retrain to C#, then the impact will be minimal, it is after all just semantics in the visual editor!

There is still a school however, that will always use C++, and I don't mean the .NET version. C++ is undoubtably the most powerful language, and is available on all platforms. However with that power comes great responsibility! :-) only joking, but with the increased power you also have increased complexity, and if you are not used to the C language it can be fairly hard to learn.

If you want to learn about Object Orientation, in a fairly similar environment to what you already know then learn VB.NET. It will give you good grounding for OO principles. Plus the .NET framework will become ubiquitous fairly soon.

Anyway that's my thoughts on the subject, sorry for rambling on a little!


  Gaz 25 09:34 25 Jan 05

I have just downloaded the beta version of Microsofts Visual Studio 2005 .NET, seems it is completly free and operative too. :-)

Most probably, final will cost, but beta works fine - reliable enough for me anyway.

The limitations were in applications that required more complex procedure's - and I did find it a little out-dated when working with XP, etc. For example, XP manifest must be enabled to allow XP styles, whereas .NET does it anyway.

Most mainstream software isn't as yet using .NET, and if the future holds .NET - it might take me that long to develop the application I wish to produce anyway...

I've been learning V6 for a few year's - I actually checked this forum for advice back then. I find this new .NET version just a bit different - and some variables have changed too. :-( Another set of learning to do.

I'm not completly bothered about Linux, because if I wanted to program something for linux - you can use a text editor and a compiler + as for linux, I don't know as much about it, as I do windows.

Thanks for the information, it was a great help. I think for the moment I'll use .NET 2005 beta and see how I get on.


This thread is now locked and can not be replied to.

Microsoft Surface PC release date, price and specs: All-in-one Surface PC to directly rival iMac

1995-2015: How technology has changed the world in 20 years

Best Photoshop video tutorials: 8 video tutorial websites for Photoshop

Apple's event invitations decoded: A look back at 16 of Apple's most cryptic invites | Clues in…