|
That's our case too. Wishing for those apps to die, but it just seems like they never will...
Enhance the trance
|
|
|
|
|
We (ok, at my _previous_ work, i dont technically have one now) had a VB.Net application that was no longer being developed, just maintained. All new things done in C#.
|
|
|
|
|
We are using VBA to plug our client-side C++ code into MS Word, but I guess it is not "real" VB.
|
|
|
|
|
Its the only VB I deal with, we have a couple little Access Forms applications, which are of course in VBA.
|
|
|
|
|
VB has left the building where I work about two years ago. Personally I didn't dislike VB.NET, it's just that C# has some more tricks and is more common here
WM.
What about weapons of mass-construction?
"What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
|
|
|
|
|
The royal We, in this case. WE touched some VB6 stuff ages ago, and was sufficiently touched by it that WE will never program in it again unless WE are starving.
Thyme In The CountryInteracxPeople are just notoriously impossible. --DavidCrow There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith
|
|
|
|
|
VB6 was a good choice for many. I programmed DOS with C, but for Windows it was far easier to use VB6 than C (I'm not a masochist, you see...). Now, with .NET Framework, C# is my only choice.
|
|
|
|
|
sect/order. They like to call themselves "we".
--
Raaaaaaaaaaaaaaaaaaaaa!
|
|
|
|
|
I had a bad experience with VB few years ago. After years of programming in C++ I tried to write a VB code with few lines. It took me two hours to understand why my code was not running. I added semicolons at the end of the lines!!! and VB didn't generate a meaningful error message about this. My conclusion is that VB is not for me. I use C#.
A good article about VB vs C# is Not Another C# Versus VB Article[^] by Nigel Shaw.
I heard once in a user group forum that Microsoft aims the .net languages as follows:
VB.NET - For quick and dirty applications
Managed C++ - For programmers who wants to fully control their code
C# - In between the aboves.
Regards,
Ami
|
|
|
|
|
u r one of the lucky ones. I just cannot seem to get the hang of C# and C++. LOL.
|
|
|
|
|
Ami Bar wrote: VB.NET - For quick and dirty applications
VB'ers prefer the term "rapid prototyping" to "quick and dirty". It makes them sound more grown-up and important than they really are
Ami Bar wrote: Managed C++ - For programmers who wants to fully control their code
That's a contradiction - if code is "managed", the programmer doesn't have full control his code. Whoever said that is an idiot.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Managed C++ means "full control relative to .NET," i.e., MC++ or C++/CLI is the "systems" language for .NET, analogous to C++ being the systems language for unmanaged code.
Kevin
|
|
|
|
|
C# is the best,dont think about the rest
|
|
|
|
|
i won't start a "what language is best" war, but saying so is simply reducing the interrest of other languages. each language has its advantages, depending on the situation (yeah, even VB6 and VB.NET, even if I don't use them).
for my part, C++ fits me best
|
|
|
|
|
I wonder who needs VB.Net since C# is easier to learn and use then VB.Net.
Me wears my armor and hides in a gutter!
|
|
|
|
|
Wong Shao Voon wrote: I wonder who needs VB.Net
1. Those who are already proficient in VB6
2. Those who must work with infrastructures already written in VB
3. Those who decide to move to VB.NET in order to make it easier to find developers. There are more developers proficient in VB.NET than C#
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
i thought C# and VB.Net are pretty much the same - just a different syntax.
i use VB.Net because i prefer the syntax, although i am also fluent in C#.
|
|
|
|
|
GuardianStorm wrote: i use VB.Net because i prefer the syntax, although i am also fluent in C#.
I use C# because I prefer the syntax, although I am also fluent in VB .NET.
Kevin
|
|
|
|
|
Chris Maunder wrote: There are more developers proficient in VB.NET than C#
Is it really true? I don't think so.
|
|
|
|
|
Rama Krishna Vavilala wrote: Is it really true? I don't think so.
AFAIK, it is true - speaking as a former moderator of a .NET forum.
|
|
|
|
|
Rama Krishna Vavilala wrote: Is it really true? I don't think so
I agree I think the number of c# developers outweighs the VB.net users considerably.
.net is a box of never ending treasures, every day I get find another gem.
|
|
|
|
|
It's not the Language, it's the Programmer.
Every Language has been created for specific Domain's of usage. Some are more Domain generic than others, but try to do something that wasn't intended for the language and you will have a hell of a time. Fortran was created for Scientific and Engineering Applications, Perl, it was intended original to be a Report generator language.
VB it was and idea from Microsoft to make it easy to develop simple to medium complexity applications in Windows, If we remember when VB came out it was two ways to create Windows Apps, or using C++ and the MFC or VB. At the moment it was wonderful be able to create a button or a window in such a simple way.
The problem comes out when we Developers try to solve any problem with only one language. And Managers that are trying to standardize the development process with only one language, thinking that in that will be more productive.
For the person that only knows how to use a Hammer, everything is a Nail.
|
|
|
|
|
It all depends on the nature of the problem you are trying to address. No language is "best."
Kevin
|
|
|
|
|
atarikg wrote: C# is the best,dont think about the rest
May be you need to write a lot more to support your point... even then it won't be sufficient to convince me...
Imagine, with the Help of VB6 (simplicity & RAD techniques)... I wrote my first Windows App (with mouse move actions, buttons, text boxes, combo boxes etc.,) in just half-an-hour back in 1998 (during when I did not even know much about Windows Operating System)
After some time with VB6.. switched to VC++ (Win32 as well as MFC)... bit of a tough start but results were worth it...
Still VB6 is a beginners language of this decade (similar to BASICs in 80s & start of 90s) I would say...!
Had I stick on to VB6... VB.NET would have been my choice.
|
|
|
|
|
We use VB for short, quick inhouse projects only.
Regards,
Gautam Jain
|
|
|
|