|
VB and C# are both .NET. The biggest difference is some syntax.
If you know your stuff syntax shouldn't be a problem.
I started out in VB.NET and I love it. There's a lot of undeserved hate towards VB.
That said I started doing C# because it's much more main stream. After about a month of working in C# it just came natural.
|
|
|
|
|
Learn C#, C++ or Java. In your case, C# is the best bet.
Sure, there are other languages, but they are secondary, so have fun finding work after that first job.
Oh, and learn punctuation and how to use the shift key. Based on your writing, I'd toss your resume in the trash no matter what languages you knew.
|
|
|
|
|
Well I go with the suck it up response. I came up via VB, in the early 00s I took the team, 5 developers, from VB to c# because that is what the market wants and that is what most of the support resources are coded in. The more time you spend working in c# the more comfortable you will get.
So stop moaning, suck it up, and get on with it!
And 'bro' is not a sign of respect in most cultures.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
C# is not better than VB.Net, they both run on top of the same .Net stack. The rest is just syntax candy. Saying that I can write in C# or VB.Net and generally I write in C# as I prefer the syntax.
In the end its a job and the best choice is where the market demand is and that is generally in C#.
Why not learn C#, if you know VB.Net you need to learn the syntax but you already know the framework, it's what I did.
|
|
|
|
|
I have a VB background: VB 3, 4, 5, 6, VB.NET (MCSD for VB5, 6, and VB.NET)
I moved over to C# in 2007 exclusively.
Well, I was kinda forced to by my, then, employer.
I have not missed VB one iota.
MS can go ahead and kill VB 
|
|
|
|
|
Pardon if this thread start is satire.
Because of years I spent developing tactical software in VBA and SQL, I found it easy to first convert to VB.NET and then C#. Not you personally, but if you cannot program in either, I find it funny, and privately think less of you, although one must consider the language barrier as an explanation. And I have met people that can only code in one, but because no one in my world codes VB.NET, it always happens to be C# people. A platform is a platform, and although there are some idiosyncrasies, the bulk of code can be written easily in one as the written in the other.
Also, please note, the VB.NET demand, according to Tiobe's index, is increasing, although my guess its usage in buried under ASP.NET and related technologies.
modified 12-Jun-15 9:08am.
|
|
|
|
|
To all the VB haters: Everyone always gives "On Error Resume Next" as the example of why VB is so horrible. Yes, using that is horrible coding - absolutely zero argument on that point.
But remember that this technique is generations old. Best Practice absolutely encourages Try/Catch - maybe MS should have removed support for the old methods, but if they did then you can imagine the backlash from developers who are trying to migrate older code. Everyone would be complaining that MS has failed to support effective migration!
Every language evolves, as has VB. Damn near 100% of the complaints that I see about VB are about the coder and not the framework. I've seen crap code in every language out there. I do agree that there's likely the perception that there is more crap code in VB, but I also believe a lot of that can be attributed to the number of programs that were written in VB historically, many by younger developers learning to code. Who on this forum believes, for one minute, that ALL C# code is being written by experienced developers? I can guarantee that in the years ahead we'll all be looking back at all the green developers that have been thrown into C# projects and seeing a flood of complaints about their crap code as well. No different than PHP or Ruby.
Crap code isn't just good error trapping, it's also consistent naming conventions, adequate comments, good class structure, proper OOP, effective use of patterns, etc. VB supports all this just as well as C#. VB will NOT stop someone from writing bad code. Neither will C# - at best it reduces, by a VERY small fraction, the opportunity for writing some bad code. But when you consider all of the things that can make bad code, it doesn't take long to realize that C# can't stop 99.9% of it. Buying a Ferrari doesn't make someone a better driver.
/endrant
To the OP: If you like VB, great. I will say that, these days (as you are discovering), it is likely becoming harder to find work in that field. And whether you decide to push towards C# or some other platform you have to recognize that, as a developer, you will constantly need to be learning and that (very important) over your lifetime you will have to learn new platforms or risk becoming obsolete and out of work. That has nothing to do with VB... the same fate can befall you in any platform. Be prepared to continue learning - it's the nature of this career path. If you find work in VB, great, but I would still encourage taking the time to continue your C# learning. I don't agree that it's light-years better than VB (as others seem to believe), but the reality is that it's where the market is right now and sooner or later you will have to accept that fact.
Best of luck.
|
|
|
|
|
Your question is a good one!
1) Last year MS rebuilt VB.Net from the ground up for VS 2015. With that level of effort, VB.Net is not going away.
2) When MS first developed .Net, they created the C# language to mimic Java. The plan was to entice Java developers to begin working with MS's .Net in VS. That plan worked!
3) The first C# developers had Java experience. This meant that they were already experienced and professional. The first VB.Net developers had experience with VB6, and some of them were individual developers, and some came from companies. So, the average experience level among new C# developers was higher than the average experience level among new VB.Net developers.
4) The early versions of C# and VB.Net had a lot of differences. Developers from both languages persistently asked MS to include features from the other language into theirs. MS began doing this (with VS 2010) with each new release. Today, the languages have far fewer differences - so the choice of language is a objectively arbitrary.
5) VS allows a solution to be made of multiple projects, and each project must use only one language. Projects within a solution can use different languages - so a solution doesn't have to be all C# or all VB.Net.
6) Some C# developers sometimes take the opportunity to be derisive toward VB.Net developers and the VB.Net language. Ignore it. Between C# and VB.Net, today's developers are all good, regardless of which language they program in. One developer putting down a language or a developer just because of a language difference is a clear sign of emotional immaturity. When you hear something like that you've learned something about the developer, not about the languages.
The reason you are finding more work with C# over VB.Net is due to the history of the two languages, not due to either language, as they work today, being better than the other language.
Learning both languages makes you more valuable - you'll be available for more jobs. You'll know that you can always find work, but you can always get the work you want when you find it.
Best of luck!
Dan
|
|
|
|
|
|
First,
This is perfectly natural. BASIC was the first language I learned, but C was always my true love. I learned Macro-11 Assembly on a PDP/11 and the C language was developed against an earlier version of this Assembler. So when I start reading in C, I felt the power, and loved the simplicity.
Second,
To switch, requires immersion. You should start READING C# projects, and tons of them. Keep reading them, and reading them. You should read each line, and know what it is in VB.Net. But keep reading it in C#. Like learning a second spoken language, at first, you will translate to understand. But once you "know" the implication/meaning of specific lines, you will no longer translate them. then, soon, you will no longer translate 3-5 lines at a time. Finally, you will be FLUENT enough.
Third,
Join a Dojo type site that asks you to solve problems using C#.
Like a child starts with alphabets, and then small words, start with the easiest problems. Solve them in C#, and keep at it. I would say 1hr a day, every day. More if you can do it.
In about 30-60 days, your comfort with C# should be significantly better.
And keep at it. Until your first thought of a new problem is how you would do it in C#
that is when you have graduated to the first level.
The point is that your love for VB is your love for its familiarity. It rolls off of your tongue, so to speak. But the market knows best, and VB is not it. VB Is good for beginners. And hence your dilemma.
|
|
|
|
|
Forget all the haters.
VB.net is a great echo system; unfortunately it got the name "VB" in it and the holy wars happened. The MS started pushing C# as the end all be all, but vb.net and C# are equivalent. the second issue for the holly war is C# name (and code) looks like C, C++; so people (shops) tend to equate C# = C++ (fast and efficient) and VB.net = VB6 (hobbyist and interpreted code).
It's stupid, I know. We all (should) know C#=VB.net close to 95%; one is not faster then the other since they both exist on the same runtime.
If VB.net had been named something like: N# and C# named something like O#, no one would be having this argument right now. and equal shops would be hiring for both N# and O#; preference being if you like "}" or "end sub"
That said we all have to work; so you do what you have to. Luckily I work for a place that let me choose the direction for all new projects; so it's almost always VB.net. But I still like messing with C (sorry guys C++ feels too messy too me) and Dlang.org looks promising.
|
|
|
|
|
For me it has nothing to do with hate; it has to do with getting a [good paying] job doing the kind of work you enjoy. For example, even though I know C# quite well, I de-emphasize it on my resume because I don't enjoy working with the web (I prefer C++ in the embedded space where someone else is worrying about the UI and the drivers--not easy to find work, but that space is what I've always enjoyed working in, starting with Assembly language, moving to C and now C++ with some C# mixed in.)
|
|
|
|
|
Yes there is difference only of names. Many times when i talk to non programmers about langauges and tell them about visual basic they always focus on word "basic" and think it is a basic language only and it is not advanced language it is just basic language.
While C# reputation is hidden in it,s name, when people listen c# they think it is C/C++ or same like this.
|
|
|
|
|
VB is much more humane. C like languages are for technoids. VB is more DSL. C like languages are "hw" oriented. The original VB had great success, but unfortunately MS choked him and ceased to evolve. And he did not even open source. Why? Still there is no VB equivalent in .net. I mean holy trinity VB & VBA & VBS. It's just not in .net. For those who still do not believe just fast example: Execute, ExecuteGlobal and Eval ... Fortunately there is a jQuery ANGULARJS and other seasonings. The only thing I miss them is case-insensitive. Case sensitive is the sheer poverty of thought. No contribution to the quality of programs and nerves of programmers. Anyway, it discards the compiler and converts to numero For example, filename in MSWindows and emails are case insensitive. And so it should be. When a MS VB hiding, never mind. There is BPMN, Angular, Node, Mongo and more. One family of open source and more. When you pardon case insensitive, so it can be a very nice HIGH-level programming.
|
|
|
|
|
Don't listen to the VB haters , they know not what they speak.I've been developing with VB since it's inception and I've never been busier. 2014 was the 2nd best year for revenue in my 40 years of working. I regularly turn down work I'm so busy. Email me direct and I'll gladly point you in the right direction.
|
|
|
|
|
Your confusion is understandable. However, we should get some basic myths out of the way so you can understand your confusion.
First and foremost, there is no difference in performance capability between VB.NET and C# as they both compile directly to the .NET Framework, which is what processes all of the compilations. There may be some minor differences in terms of how specific areas of code are defined but that is about it.
Two, as a result of the first item, the only major difference between VB.NET and C# is the syntax.
Three, the syntax of both languages are completely convertible to the other with some minor differences in conversion capabilities with specific code. There are several free online conversion utilities that provide such services that you can avail yourself of. One good one is found at http://www.developerfusion.com.
The commenters here that suggest you work in C# professionally while doing your personal projects in VB.NET is a very legitimate suggestion.
Many software professionals and companies prefer C# over VB.NET for the most nonsensical reasons; the most common one being that it is believed that C/C++ syntax, which C# mirrors, is superior and cleaner whereas VB.NET syntax is considered too verbose. They are correct but who cares? Its not the syntax that executes any application.
Like you, I much prefer VB.NET but then I am a product of the 4th generation languages that were highly popular in the DBASE world when it was the king of software development. However, I am just as fluent in C#.
Learn C# simply by reviewing how easy it is to simply move VB.NET code into C# syntax for the most part. There are differences but if you use VB.NET as a guide you should feel a natural affinity for C# in a few months. Then you will be "multi lingual" and more adept at securing employment...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
half the problem is there are too many coding snobs who think vb is some poor relation to c# but its the skill of the programmer that counts and a poor coder will always be a poor coder no matter what the language. i've written commercial apps in every incarnation of vb since the 70's and never had a problem, selling many thousands of copies as well as larger bespoke commissions. VB.NET compiles to the same IL as any .NET language so there's no speed issues, and ive never needed to change, my customers don't even ask what language its written in, they are only concerned with the results. Broaden your searches and follow your instinct of what you wish to do. GL
|
|
|
|
|
VB made you soft and weak, now you pay the price for ignoring advice.
|
|
|
|
|
How vb made me soft and weak?
|
|
|
|
|
I have similar sentiments and history. I started (professionally) in VB 3/4 back in the late 90s. I also know a dozen different languages and several platforms. I was forced into C# about 3ish years ago. The kicker is I actually agreed with the move; it made good business sense… and made me a bit sad. I’ll always be in love with BASIC. Its current face is VB.NET, but who knows where that’ll be in the future.
The simple truth is that Microsoft backs C# more than VB. As I recall, in .Net Rocks Episode # 1140 (@ 43 minutes) Jay Schmelzer talks about how new language features will usually be in C# first, then added to the others. It’s sucks, but that’s the way it is. Quell the automatic reaction and ask yourself why. My opinion is that it is Java’s fault. Microsoft is trying to attract Java devs to .NET. C# can get that job done, VB can’t.
Quote: Many peoples told that c# is better than vb.net...
Anybody who says C# is “better” than VB.net is an idiot. (Or even VB.net is “better” than C#) They simply don’t understand the .NET platform. Inform them if you can, but try not to argue. It’ll make you look as dumb as them. Microsoft’s brilliance is .NET… not VB, C#, or F#. They are just tools.
Quote: But problem is that i can,t code in c# same as in vb.net
I also tended to write code in VB, and then translate into to C#. Practice will make it more nature.
Quote: I love vb but what should i do while markete don,t have demand of vb?
People still write COBOL!!! They’re not as many COBOL jobs today, but they still exist. They’ll also be harder to find. I’d suggest figuring out what you want to do: be a VB.NET specialist or a generalist able to do both VB and C#. Then take a look at the job market(s) you have access to. Do enough possible jobs exist to support a specialist? If it does, then raise your rates and apply. If it doesn’t, well, either become a generalist or move to a different market.
- great coders make code look easy
- When humans are doing things computers could be doing instead, the computers get together late at night and laugh at us. - ¿Neal Ford?
|
|
|
|
|
You spoke golden words. It is really nice answer that if markete have demand of vb specialist then i should become vb specialist other wise i should be a generalist and should work in both vb and c#. But here c# has more preference so i should become generalist. But it is reality i can code more better than c#.
|
|
|
|
|
You go right ahead and stick with VB if that's what you're comfortable writing (particularly if you're 'on your own' consulting. The client doesn't care what language you use!) I've written (and still do) professional VB (both VB6 and .Net) as well as a lot of C#. I write some Javascript, spent about 15 years writing C/C++ and a dozen or so writing assembly, and even FORTRAN (back in the 'old' days). Unless you're in some shop that REQUIRES you use a particular language for development (or trying to impress someone with esoteric or terse looking code) rather than getting RESULTS then, as I said, use the one you like. Personally I think VB has some real charm to it (as well as being just as functional as C#). There's a lot of language bigots out there. Just ignore them.
-CM
|
|
|
|
|
It took only one month to change my heart's desire from VB.NET to C#. Try learning C# and will find you can do everything you did with VB.NET.
|
|
|
|
|
I don't understand this. VB.NET is virtually intrinsically the same as C#, just in a C-style syntax rather than a BASIC-style one. The main difference is that function calls & signature definitions are encased in parentheses, and code blocks, including function & class blocks and namespaces, are encased in squiggly brackets {}. Once you incorporate this, there isn't a whole lot more to learn.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)