vb.net vs. c#

[basti42]

which is better vb.net or c#?

[DigiRev]

C# or C#.net?

Also, better for what?

[RhinoBull]

For what it's worth:

in the .Net framework language is irrelevant since they all based on the CLR (common language runtime).
It's all about which syntax you are more familiar with...

[basti42]

what i mean is vb.net vs. c#.net?

[RhinoBull]

I answered already.

[RobDog888]

Moved

Its just a matter of which "front end" you want to use as posted, they both run on the same exact framework.

[jmcilhinney]

C# or C#.net?

Also, better for what?

There's only one C#.

Also, there is a little more to it than just what front end you prefer. There is far less of a difference between VB.NET and C# than there used to be between Microsoft's two primary languages, VB6 and C++. The commonality created by multiple languages using the one Framework means there is a lot of similarity and overlap between all .NET langauges. VB.NET is still aimed more towards the low end and C# towards the high end.

The VB.NET syntax is intended to be more readable to non-technical people. Also the language and IDE provide various features to automate certain tasks that would require writing code in C#, like single-instance applications and spalsh screens.

C# provides some powerful features that VB.NET doesn't, most notably support for pointers.

If all the world's .NET developers were spread out on a scale from zero to 100, with zero being the least able and 100 being the most able, I'd say that VB.NET covers from zero to 90, while C# covers from 10 to 100.

If you have no programming experience and are just intending to mess around then I'd suggest VB.NET. If you want or need as much power as possible then I'd suggest C#. If you're somewhere in the middle then I'd suggest either or both.

[RobDog888]

There is more then one and more then one for a reason. You need to use the best tool (language) for the project/job. You can do everything in either language, just depends on how much code you want to write and how hard you want to work. Where there is a will there is a way to come up with supplemental workarounds that basically equate the .NET languages (except J# since its relativetitly new and under developed).

If there was only one language, then it would be a sad day for all .NET programmers.

[shakti5385]

As JMC Say about the c#.NET then what is better that the shift all the work in the C#.NET or if you are working in the VB.NET then it is enough for you??

[RobDog888]

No, it depends on your project, budget, and timeline. Like I posted its best to use the proper tool for the job.

[mendhak]

In addition, this is a topic that has been discussed, but not apparently to death. Which means that you will find several very useful discussions if you do a search on it in these forums.

[Gameunreal]

.. many many because when i came here asking the same question jmcilhinney posted about 30 links...