Advantages of converting Vb.net project to C#

[Rajesh]

Any idea?

 

[Michael D. Ober]

Only if you're already a C# programmer. VB.NET and C# are very nearly
functionally equivalent with VB being easier to read. As for anyone who
says that VB isn't a "professional" language, it's interesting to note that
it was VB and not C# that was used in the Denver, CO VS 2005 Launch Event
developer's track.

Mike Ober.

 

[Jeroen Vandezande]

Only if you're already a C# programmer. VB.NET and C# are very nearly
functionally equivalent with VB being easier to read. As for anyone who
says that VB isn't a "professional" language, it's interesting to note
that
it was VB and not C# that was used in the Denver, CO VS 2005 Launch Event
developer's track.

I totaly agree!
The great thing about .net is that you can choose your favorite programming
Language and the resulting app will probably run at the same speed.
I for example use Chrome + VS2005 to program for the .net framework because
I come from a Pascal background.
Use the Language you are comfortable working with...

Best Regards,

Jeroen Vandezande.

 

[Daniel O'Connell [C# MVP]]

Only if you're already a C# programmer. VB.NET and C# are very nearly
functionally equivalent with VB being easier to read. As for anyone who

Well, they are nearly functionally equivilent anyway. Assuming you actually
know both languages or their root languages, VB and C# are nearly equally
readable when well written, and horrible when badly written, with personal
preference pushing you one way or the other. Personally I find VB messy and
oddly designed, I'd would rather not use it. Its not that its
unprofessional, I just find it unpleasent.

If you don't know any computer language you are going to be wrong and make
quite a few mistakes in VB as well as C#, for example the meaning of shadows
or the use of optional parameters or indexed properties that look like
methods and so on. VB merely looks extremely simple, it really isn't. It has
its ghosts and traps like every language.

 

[Guest]

It's all a matter of preference. I could list the handful of things you can
do in C#, but not in VB and vice versa, but it would still boil down to
preference. Performance is virtually identical.
--
David Anton
www.tangiblesoftwaresolutions.com
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: C# to C++ converter & VB to C++ converter
Instant J#: VB to J# converter

 

[Kevin Spencer]

The only benefit you would get would be the experience you gain from doing
so, and, if you don't know C#, whatever you would learn about the C#
language in the process.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Who is Mighty Abbott?
A twin turret scalawag.

 

[Rajesh]

David,

You said " I could list the handful of things you can do in C#, but not in
VB" can you kindly list out?

Raj

 

[Jon Skeet [C# MVP]]

You said " I could list the handful of things you can do in C#, but not in
VB" can you kindly list out?

See http://www.pobox.com/~skeet/csharp/faq/#vb.or.csharp for a list
(albeit incomplete).