|
|
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.
|
|
|
|
|
|
Did you already hear about Leslie?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
I don't really care about Leslie. (I would if subjects were meaningful)
I'd rather be phishing!
|
|
|
|
|
Ready in Production?
Can't just write what Nagy already did, like it's very sad he died?
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
*lowers glasses and looks over the top*
veni bibi saltavi
|
|
|
|
|
They say...
Conference Dress
Attire for the conference is business casual.
Your mission, should you decide to accept it, is to guess what that means.
Wait !
I got it !
I'll ask Wikipedia ! Yes ! Then I will be the best dressed man at the conference !
|
|
|
|
|
Well, since it says "casual", I think you can rule out a tuxedo... And since it says "attire", you can rule out nudity.
So the answer must lie somewhere between those two.
|
|
|
|
|
Wear a tie.
That should cover it. (Hopefully, if it's a big enough tie)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: (Hopefully, if it's a big enough tie)
That's called a napkin and you 'wear' it (if at all) only to lunch or dinner.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|