Quote:Original post by SiCrane
There isn't any reason not to try both C# and VB .NET out. I personally prefer C#, but I will admit that Intellisense for VB .NET seems to be better. No clue why that is though. Maybe when the final version .NET 2005 gets released there will be better parity there.

Trying out the 2005 beta, the C# intellisense is quite good. It will pop up when you are defining something (the actual type), which is nice for me coming from VB... Can't wait for it to come out on shelves.

Quote:Original post by SiCrane
I personally prefer C#, but I will admit that Intellisense for VB .NET seems to be better.

I suspect it's because the VB syntax is a bit more suggestive. Consider variable declarations -- they prompt for a type, whereas in C# there is no way intellisense could give you a type list for variables without you pulling up the list manually.

I think VB has always been about providing a reasonably quick way of getting prototype apps up and running. "rapid application development" if you like. Would you want to sell anything written in it? Well maybe, but the answer is predominantly no. If you need to knock out a quick and dirty tool for a tight deadline, it's a language to consider. The fact that it shares a lot of the same properties as C# makes for a simplified job of porting it. As to the benefits of C#, I have no idea.

Quote:Original post by DrewGreen
I think VB has always been about providing a reasonably quick way of getting prototype apps up and running. "rapid application development" if you like. Would you want to sell anything written in it? Well maybe, but the answer is predominantly no. If you need to knock out a quick and dirty tool for a tight deadline, it's a language to consider. The fact that it shares a lot of the same properties as C# makes for a simplified job of porting it. As to the benefits of C#, I have no idea.

VB.Net is a full featured language, and you would definitely want to sell anything written in it provided it works and is useful. Enough of the old "VB is not cool 'cause it's easier to get into." In fact I would pick an app written in VB.NET over the same app written in C++ anyday, if only for the fact that I'm sure the OS won't have to clean a huge mess at the end.

Quote:Original post by xMcBaiNx
Enough of the old "VB is not cool 'cause it's easier to get into."

That's not what I said.
VB is a useful language & I use it for my own projects. It was also one of the first languages I chose to learn when I was starting out. It has it's benefits. The one I value most highly is the gui design features. It also has it's flaws. If you are looking for raw speed, you will never find it in VB. Perhaps that's changed since the introduction of the .net framework but as far as I'm aware it's still interpreted, and does nothing to encourage efficient program design. It is not a fully featured language either. There may well be additions such as linked list classes in the new editions but the ability to define your own *new* abstract data types without primitives such as pointers is severely limited. (and no, that isn't a "VB doesn't have pointers" comment.)
This may seem like I'm contradicting what I've just said but I personally found learning C to be a big challenge after being used to many years developing in a BASIC language.

In any case in a commercial environment where time is money, VB is a very desirable tool to use.