What is going on. When c# first came out M$ was pushing users to move to that. Now I see an article that show that you can now translate c# to vb.net.
http://msdn.microsoft.com/vbasic/default.aspx pull=/msdnmag/issues/06/02/PasteAs/default.aspx
why does it seem like vb.net is being pushed so much more in the 2005 version. I just decided to move to c# from vb.net because of the following.
1.forced declaration of variables
2. told it was better language for businesses (reguardless that vb can do the same)
3. was told c# is more professional where vb.net was used more as hobbiest.
4. Pay is larger
5. More companies were moving to it.
6. Makes you become a better programmer.
Was everything I ever read wrong
I know both, but have be centralizing all my new programs to c# because of hearing it was a better choice between the 2. Now I am seeing M$ really pushing vb.net.
Need to hear what everyone has to say.
c# to vb.net
Fiumag
GizmoGorilla
I guess the other thing to remember is, VB fans have always touted how many people 'use' VB, in whatever form. The flip side is, how many VB programs do people have running on their desktops Not many. VB is widely used in house to quickly write business apps for closed client bases, and by hobbiests.
I would agree that I wish VB.NET did not exist ( I've also been stuck in the hell of VB6, AND VB.NET at times ). However, I can see why it does. The outcry over the death of VB6 has been loud enough without VB being put to pasture altogether.
maara
JohnyHandSome
I guess first 1 thing was this.
http://msdn.microsoft.com/vbasic/default.aspx pull=/msdnmag/issues/06/02/PasteAs/default.aspx
where a vb.net to c# mentioned by msdn.
2nd there is a ton more articles dealing with vb.net
if u look at the c# page there is a link on it talking about learning vb.net, on c# homepage. At the launch of the new vs 2005. Most all examples where shown in vb.net instead of c#.
even the refactoring add-in for vb.net is considered better by several articles I have read.
More time put in vb.net with snippets, forms templates.
I am just worried that since I finally decided to make business applications in c3 instead of vb.net that I might have made the wrong decision. I also notice that j# is not even really mentioned anymore. Almost like it is dying. Do u think c# will end up going the route j# is. I am just asking.... I guess M$ has made me question there feelings toward c#.
That's all. this is why I am posting this question. I just dont know so please dont think I am questioning or pointing to facts. I am just looking for answers, that;s all
programmerInprogress
Janet Robinson
I think I saw this article too. We have a to remember that Microsoft is a large organisation and therefore has its own VB and C# advocates. I do not believe, and choose not to believe, that "the majority of programmers use vb.net". This is what being forced to use VB6 can do to you. And there are plenty of things in VB .Net that I think are just wrong - case insensitivity, verbosity, yada, yada
Enkore
First of all, it's always been possible to move from C# to VB.NET, and vice versa, there are numerous commercial tools that do it. I bought a VB.NET -> C# converter, because if I get offered VB.NET work, I refuse unless I can move it to C#.
I don't think VB.NET is being pushed over C# at all, what makes you say that
1 - yes, I agree
2 - More professional in what way VB.NET will always have the stigma of VB6 associated with it, but the truth is, you can write apps in either that do the same. They both have bits of sugar that the other lacks, although VB.NET would be better without the legacy VB6 stuff Microsoft were forced to support
3 - Actually, the number of people using VB.NET in business is huge, because they all moved from VB6. Although, I have to say, no-one in any of the places I work would consider using it.
4 - I have no idea about that. I do know that managers I've pitched to regard VB developers as being cheap and easy to find, so perhaps it is so. I've seen some huge paying VB jobs tho.
5 - that's possible
6 - I would say this is almost certainly the case, mostly because C# is strongly typed and doesn't have any sort of legacy stuff, being brand new.
I'm interested to see how you think MS is pushing VB over C#. If they are, doesn't that mean they need to ( i.e. that people are using C# ) Either way, I would never choose a language based on marketing. I use C++ because it's powerful and C# because it was an easier fit given my C++ background when I need to use the .NET framework.
marek.dziedzic
As I said VB.NET to C# and vice versa is old news. It works both ways. I see people every day who use VB.NET trying to use C# code snippets they find. I see less people using C# who cannot work out how to convert a VB.NET code snippet if they find one.
J# is obviously the one that is barely used :-) J# is a Java like language, because Microsoft is not allowed to actually do a Java implimentation ( I believe ). C# is Microsoft's new language, which is standardised. I would bet any body part you'd care to mention that neither VB.NET or C# is going anywhere anytime remotely soon. I was personally betting on the demise of VB, but I'm pretty sure now that I was wrong.
You have to consider the possibility that VB.NET users get more help because they need it....
J.auger
You're utterly wrong. Sorry :-)
(sorry, this was to the guy who said you can only use VB in SQL Server, not the guy who also corrected him. That's what I get for not reading the whole thread first... )
Carlos Garcia
Personally I wish Microsoft had never invented VB .Net. I think it is a mistake to split their development and support between two different languages, no matter how similar. VB .Net was a sop to the VB6 programmers to make them move to .Net, but the biggest challenge is not in learning the language (C# or VB .Net) but in the framework. It would have been better for everyone if Microsoft had just given us C# and the VB guys had to bite the bullet. By now everyone would be quite happy using C#.
Can you tell I've been force to use VB6 in the past, and I hated it (don't get me started...)