which is preferable
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
Singan wrote:
my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#.
This argument is specious. You can screw up multi-threading just as easily in C# as you can in VB.
Singan wrote:
I'm absolutly not a expert on the subject
Singan wrote:
my friends tell me
Singan wrote:
So I say use C#
Indeed. :|
Man who stand on hill with mouth open wait long time for roast duck to drop in
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
Singan wrote:
To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work'
Sorry, but that is totally untrue, unless they discovered a bug in the VB.NET compiler. Threading is handled by the CLR, and it knows nothing about VB.NET or C#, only MSIL.
Regards Senthil [MVP - Visual C#] _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
Thanks Singan, when there is Visual studio , we used to use Visual Basic that is the only front end we used to use. and i used to do automation project in Visual basic . now i am planning to do some projects to .NET so i am confused which one to use C# or VB.NET because both provide window application and both looks really the same . both provide data base connectivity and reporting tools etc.. so i thought of asking experts this forum.
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
Singan wrote:
I'm absolutly not a expert on the subject
Singan wrote:
my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#.
Singan wrote:
To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work'
Singan wrote:
So I say use C# because you probably sooner or later like to use this solutions.
There's nothing like arguing a case from a position of no knowledge. This argument is complete and utter rubbish - in fact, it's been a long time since I've heard an argument that is so completely wrong, that it has a degree in wrongness. You do know that threading is a capability of the OS (and encapsulated by the framework on top) don't you? Given that, you do know that there isn't a VB only version of the .NET runtime don't you. So, stop relying on other people to do your thinking for you, and start thinking for yourself. Any idea that starts with "this bloke told me" is almost always guaranteed to be wrong.
"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.
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
Singan wrote:
I'm absolutly not a expert on the subject
No, and...
Singan wrote:
but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#.
it appears your friends are idiots.
Christian Graus Driven to the arms of OSX by Vista. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums. I can do things with my brain that I can't even google. I can flex the front part of my brain instantly anytime I want. It can be exhausting and it even causes me vision problems for some reason. - CaptainSeeSharp
-
Thanks Singan, when there is Visual studio , we used to use Visual Basic that is the only front end we used to use. and i used to do automation project in Visual basic . now i am planning to do some projects to .NET so i am confused which one to use C# or VB.NET because both provide window application and both looks really the same . both provide data base connectivity and reporting tools etc.. so i thought of asking experts this forum.
Please ignore this idiot. He's wrong - in fact he couldn't be further off the mark if he insisted the earth was flat.
"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.
-
Singan wrote:
I'm absolutly not a expert on the subject
No, and...
Singan wrote:
but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#.
it appears your friends are idiots.
Christian Graus Driven to the arms of OSX by Vista. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums. I can do things with my brain that I can't even google. I can flex the front part of my brain instantly anytime I want. It can be exhausting and it even causes me vision problems for some reason. - CaptainSeeSharp
Christian Graus wrote:
it appears your friends are idiots.
Not only his friends - I have to assume they're his frat buddies from idiots anonymous.
"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.
-
Please ignore this idiot. He's wrong - in fact he couldn't be further off the mark if he insisted the earth was flat.
"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:
in fact he couldn't be further off the mark if he insisted the earth was flat.
I prefer listening to the arguments of the concave earth society myself. :)
Man who stand on hill with mouth open wait long time for roast duck to drop in
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
-
Please ignore this idiot. He's wrong - in fact he couldn't be further off the mark if he insisted the earth was flat.
"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:
he couldn't be further off the mark if he insisted the earth was flat.
Well said! We all know the earth is a cube.
It is a crappy thing, but it's life -^ Carlo Pallini
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
:wtf: :~ X| No. Just...no. When VB.Net is compiled, it produces CIL code. When C# is compiled, it produces almost identical CIL code (give or take some compiler-specific optimisations). Multithreading works the same in VB.Net as it does C#. If your friends think this, then they should have asked for help when they had trouble (I assume that's why they are so put off VB.Net threading) The only 'hangup' I can think of is that one has to use the AddressOf operator (if this wasn't used, then I could see how a problem would exist), but even this is fairly clear. Something that you might have misheard are the problems that legacy VB has with threads. VB.Net != VB
Between the idea And the reality Between the motion And the act Falls the Shadow
-
Hi All, i need some info regarding c# and vb.net. which one(c# or vb.net) will be good to kept as front end , back end will be a database for project like school management system or to develop any kind of automation software. i dont know which can be better one to do this kind of project. Thanks in advance .
Hi, if you were familiar with both languages you wouldn't ask, you'd just choose yourself. if you were familiar with just one of those languages, there would be no need to ask, use the one you know. so start learning C#, go buy a tutorial book and study it. :)
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get. Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
-
I'm absolutly not a expert on the subject, but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#. To be frank the tell me 'u get hangups multi threeding in VB.NET ... i doesn't work' So I say use C# because you probably sooner or later like to use this solutions.
I suggest seeking out new friends who know better and actually know how to write code. Your current crop of friends don't have a clue about what they're talking about. Did you know that VB.NET and C# compile down to the same MSIL code?? Use the same libraries in the .NET Framework?? So how could one work and not the other??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Hi All, i need some info regarding c# and vb.net. which one(c# or vb.net) will be good to kept as front end , back end will be a database for project like school management system or to develop any kind of automation software. i dont know which can be better one to do this kind of project. Thanks in advance .
Check this out http://support.microsoft.com/kb/308470[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
The woods are lovely, dark and deep, But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep! -
Check this out http://support.microsoft.com/kb/308470[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
The woods are lovely, dark and deep, But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep! -
Singan wrote:
I'm absolutly not a expert on the subject
No, and...
Singan wrote:
but my friends tell me that you get a lot of hangups when using multi threeds in VB.Net but never in C#.
it appears your friends are idiots.
Christian Graus Driven to the arms of OSX by Vista. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums. I can do things with my brain that I can't even google. I can flex the front part of my brain instantly anytime I want. It can be exhausting and it even causes me vision problems for some reason. - CaptainSeeSharp