Difference between c# and VB.Net
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
If that's the respect they show you when you don't yet work for them, what can you expect when you take the job?
I wanna be a eunuchs developer! Pass me a bread knife!
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
;
I wanna be a eunuchs developer! Pass me a bread knife!
-
Pete O'Hanlon wrote:
They are doing you the favour of interviewing you, not the other way round.
Rubbish. Or at least not the way I look at interviews. I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview. At the very least, Interviews are a 2 way process - with me interviewing the company just as equally as they are interviewing me.
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
CPallini wrote:
C# is a truly advanced language.
You're starting to make sense...
CPallini wrote:
They are functionally equivalent.
...for a short moment. Yes there are some functional overlaps. You of all people should know VB.NET doesn't offer pointers. :-D
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
Luc Pattyn wrote:
Yes there are some functional overlaps
:-D
Luc Pattyn wrote:
C# is a truly advanced language.
Luc Pattyn wrote:
VB.NET doesn't offer pointers.
:laugh:
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
J4amieC wrote:
I can take any job I please, they are looking for 1 individual. Therefore Im doing them the favour of offering my services, if they don't cut the mustard (and that includes shoddy interview/working practices) I hit the door and walk into the next interview.
In a strong employment market, this is the case. The reality, at the moment, is that I don't need to hire you - there are a lot of others who would be willing to take the job. It's a hirers market at the moment and if you need a job, you can't afford to be that choosy; unless you fancy flipping burgers.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Marcus_Idle wrote:
asked a fairly open question
My discussion was scheduled at 9:30 AM, and was done at 1:30 PM, till then I had to wait there, with out any satisfactory reasons from the HR dept. I was so frustrated when I went to the panel. Listening to the first question from the panel made me think otherwise.
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
Whatever the market, if they don't respect you enough to atleast apologise with a reason for the delay, don't bother, once you start there you will be considered cannon fodder...
____________________________________________________________ Be brave little warrior, be VERY brave
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
Actually there are at least three fundamental differences. 1. Certain functionalities are NOT exposed in VB.Net in the framework! Thereby C# is mightier ;-) 2. vb.net' "shared" key word dos not exactly behave like the static keyword in C#. I read somewhere that it has to do with the downward compatibility for old code to be portable. So VB.Net does NOT have an equivalent to the static keyword! The static keyword in C# you can trust. Shared keyword in VB.Net you can trust too but not in the same way. 3. VB.Net does not know advanced syntax like ++/-- or other short writing styles for long statements like (x=y)?a:b. In VB.Net you need to call a function IIF for such.....
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
I personally think that VB.NET and C# are only flavors of the same .NET technology. The most obvious fact is that you can compile a DLL in C# or VB.NET and use it in the other language. So MS, wanted to spread the .NET use to everyone who barely knows to use Office and created VB, for the really expert programmers, C#. So the only difference is the similarity of the code with the English language. Nevertheless, good question, I will ask it to my Programming teacher next year. :-D
-
Addenda: I myself prefer VB over C#, but I don't go around saying that C# is crap (because it isn't - just different syntax)
-
Well, not quite: VB is based on a "toy" language, invented to let non-programmers do things with computers. It has been forced in lots of different directions until it arrived, creaking at the seams, at it's current state. C# is a "new" language (as in designed with a blank sheet), taking all the lessons learnt from C, C++, VB and others to produce a modern language with modern computers in mind. It has it's faults, but at least it is what it was designed to be.
Did you know: That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
You'll be pained if you try to teach a kid how to program in C#. But if you start with VB first, then let them switch later, well...
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
Liking C# for it's syntax and ease of mind I usually find myself coding in VB at work since I think it's easier and faster for other people to get up to speed with without having to read through all sorts of documentation, it's somewhat easier to get an overview of. IMHO. :)
-
VB.NETis a crap,C#is a truly advanced language. They are functionally equivalent. :rolleyes:If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]I usually use C#. C language is more scientific than VB.net. But in some small application, VB is easier to handle.
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Pete O'Hanlon wrote:
They are doing you the favour of interviewing you, not the other way round
I don't agree, in general. Unless I would be unemployed or waiting for an interview at Google, I'd have walked away. It's called mutual respect. As much as I need to market and sell myself in an interview, the same applies to the company that wants me to work there. Anything else makes big red noisy warning lamps go off in me.
Time you enjoy wasting is not wasted time - Bertrand Russel
-
Utterly stupid and biased reply. VB and C# are ALMOST identical, there are no big differences.
Which is probably why they asked the question (giving them the benefit of the doubt) as being aware of the small differences shows attention to detail at least. Saying that, I have been asked this same question more than once in interviews, but it was a few years back, when the differences were more pronounced.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
VB and VB.net - allowing idiots to code for the past 20 years. JK
-
J a a n s wrote:
with out any satisfactory reasons from the HR dept
That's their prerogative. If, for instance, they are interviewing lots of people then they, quite frankly, don't have to give you a reason. They are doing you the favour of interviewing you, not the other way round.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Sorry Jaans, thats not the way it works. The whole idea of the employer/employee relationship is one of mutual benefit. If they mess you about looking for the right person then either its already a done deal for someone else, or the company are not interested in employee relations. I would think seriously about working for a company that displays this level of rudeness, incompetence or both.
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
-
Actually there are at least three fundamental differences. 1. Certain functionalities are NOT exposed in VB.Net in the framework! Thereby C# is mightier ;-) 2. vb.net' "shared" key word dos not exactly behave like the static keyword in C#. I read somewhere that it has to do with the downward compatibility for old code to be portable. So VB.Net does NOT have an equivalent to the static keyword! The static keyword in C# you can trust. Shared keyword in VB.Net you can trust too but not in the same way. 3. VB.Net does not know advanced syntax like ++/-- or other short writing styles for long statements like (x=y)?a:b. In VB.Net you need to call a function IIF for such.....
Let us not forget AndAlso
-
Last weekend I went for an interview in a Reputed organization. The first question from the interview panel was the difference between VB.Net and C#. I just came back!!! Can any one here spot the differences :)
"Never put off until run time what you can do at compile time." - David Gries, in "Compiler Construction for Digital Computers", circa 1969.
The real trick is answering a question like that with one word. Syntax.
-
VB and VB.net - allowing idiots to code for the past 20 years. JK
Very True. C# has only allowed idiots to make code for that last 7 years.
