I don't know if I should even start this topic but here goes.
I'm an ex vb6 developer, now developing in C#.
The reason why I started developing in C# is because the company that I
worked for at the time standarised on C#.
Many of my friends working in previous companies that I worked for are
starting to move back to VB.Net. When I asked them why, it seems that
the next release of VB.Net seems very promising and they kinda see
themselves in the same position I'm in. It seems that at the time when
..Net was first released many companies basically forced developers to
work in C# because as in my case the company they worked for
standarised on C#, why these companies did this is beyond me because
most of their developers were vb developers, I think it's because it
was marketed that C# was the main language to use on the .Net
Framework.
Now many companies as well as management in these companies are
starting to realise that vb.net is not that different from c# and are
starting to give their developers a choice and thus obviously the move
back to vb.
The reason why I'm posting this topic here is because I'm wondering how
many developers using c# are ex vb developers and would actually like
to develop in vb.net. I have actually convinced my superiors to use
vb.net as another language choice and they have agreed.
We have just started a new project in vb.net about 3 mths ago and I
must say that it's still a damn fun language to work in, I'm actually
enjoying my work again. Productivity couldn't be higher as other c# (ex
vb6) developers in my department have also wanted to go back.
Wondering how many of you out there would like to move back to the
lighter side of life? 132 5793
"Kevin" <ke***@inatrice .co.za> wrote in message
news:11******** *************@f 14g2000cwb.goog legroups.com... I don't know if I should even start this topic but here goes. I'm an ex vb6 developer, now developing in C#. The reason why I started developing in C# is because the company that I worked for at the time standarised on C#.
Many of my friends working in previous companies that I worked for are starting to move back to VB.Net. When I asked them why, it seems that the next release of VB.Net seems very promising and they kinda see themselves in the same position I'm in. It seems that at the time when .Net was first released many companies basically forced developers to work in C# because as in my case the company they worked for standarised on C#, why these companies did this is beyond me because most of their developers were vb developers, I think it's because it was marketed that C# was the main language to use on the .Net Framework.
Now many companies as well as management in these companies are starting to realise that vb.net is not that different from c# and are starting to give their developers a choice and thus obviously the move back to vb.
The reason why I'm posting this topic here is because I'm wondering how many developers using c# are ex vb developers and would actually like to develop in vb.net. I have actually convinced my superiors to use vb.net as another language choice and they have agreed.
We have just started a new project in vb.net about 3 mths ago and I must say that it's still a damn fun language to work in, I'm actually enjoying my work again. Productivity couldn't be higher as other c# (ex vb6) developers in my department have also wanted to go back.
Wondering how many of you out there would like to move back to the lighter side of life?
Well, I enjoy C# more than I do VB.Net. I originally started development in
QBasic then moved to C/C++ on *nix. From there I learned Visual Basic and
moved on to the .Net platform and learned VB.Net and C#. I just like C#,
the syntax is less wordy (no Then's or End If's), which means less typing...
and I really like the way it looks (looks and feels like C/C++).
Mythran
> Well, I enjoy C# more than I do VB.Net. I originally started development in QBasic then moved to C/C++ on *nix. From there I learned Visual Basic and moved on to the .Net platform and learned VB.Net and C#. I just like C#, the syntax is less wordy (no Then's or End If's), which means less typing... and I really like the way it looks (looks and feels like C/C++).
Mythran
Wow you've been back and forth, QBasic -> C/C++ -> Visual Basic -> C#.
I disagree with your 'less typing' statement in some respect as Then's,
End If's and even End Sub End Function are implemented for you as you
enter to the next line. Even Catch and Finally is automatically coded
for you as you hit enter after a Try statement.
I do agree with your statement about look and feel, this is exactly the
point I'm trying to make. I think look and feel is important as it, in
my mind, makes you a more productive developer because you feel
comfortable with the syntax.
But I can't help wondering if ex vb6 developers now working in C# would
be more productive going back to vb.net for this exact same reason. I
know I am.
>. I just like C#, the syntax is less wordy (no Then's or End If's), which >means less
typing...
Actually, the IDE 'types' all this anyhow, and
does a real good job of aligning it too.
So this is not really an issue.
and I really like the way it looks (looks and feels like C/C++).
May look like C/C++, but it's really quite different.
Type safety in C#, is one very much appreciated
difference.
Roger
Couldn't type safety be implemented by turning Option Strict On.
Kevin Couldn't type safety be implemented by turning Option Strict On.
Yes, but that's VB.
I was comparing type safety in C/C++, to C#
Good day,
Roger
Kevin wrote: The reason why I'm posting this topic here is because I'm wondering how many developers using c# are ex vb developers and would actually like to develop in vb.net.
I've developed in VB, VB.net, C, C shell, and various other languages,
but my main base is C and C-like languages (php, perl, etc).
Learning .net, I get to play with both VB.net and C#.net, and I have to
say, I sure hope it remains a viable option, because I never much liked
VB and it hasn't changed much. LOL
IMO, people who learned VB before C prefer VB.net and people who
learned C before VB prefer C#.
I don't think it really comes down to any more than that, regardless of
what they attempt to justify it with. But feel free to correct me. :)
(whoever came up with "on error resume next" needs to die a slow and
painful death caused by ingrown toenails...)
Having used various languages over the years (like most programmers) such as
Cobol, VB6, Perl, KSH, C, C++ and C#, etc. I just prefer c# over them all,
and its not just one or two things you can point to. But that is me.
Others will find VB.Net more to their taste and that is great. Pick the one
you like and use that.
--
William Stacey [MVP]
"Kevin" <ke***@inatrice .co.za> wrote in message
news:11******** *************@f 14g2000cwb.goog legroups.com... I don't know if I should even start this topic but here goes. I'm an ex vb6 developer, now developing in C#. The reason why I started developing in C# is because the company that I worked for at the time standarised on C#.
Many of my friends working in previous companies that I worked for are starting to move back to VB.Net. When I asked them why, it seems that the next release of VB.Net seems very promising and they kinda see themselves in the same position I'm in. It seems that at the time when .Net was first released many companies basically forced developers to work in C# because as in my case the company they worked for standarised on C#, why these companies did this is beyond me because most of their developers were vb developers, I think it's because it was marketed that C# was the main language to use on the .Net Framework.
Now many companies as well as management in these companies are starting to realise that vb.net is not that different from c# and are starting to give their developers a choice and thus obviously the move back to vb.
The reason why I'm posting this topic here is because I'm wondering how many developers using c# are ex vb developers and would actually like to develop in vb.net. I have actually convinced my superiors to use vb.net as another language choice and they have agreed.
We have just started a new project in vb.net about 3 mths ago and I must say that it's still a damn fun language to work in, I'm actually enjoying my work again. Productivity couldn't be higher as other c# (ex vb6) developers in my department have also wanted to go back.
Wondering how many of you out there would like to move back to the lighter side of life?
It's all a matter of what you want to do with your life. Now many companies as well as management in these companies are starting to realise that vb.net is not that different from c# and are starting to give their developers a choice and thus obviously the move back to vb.
You put your finger on it right there - "not that different." In fact, C#
and VB.Net ARE different, in terms of what you can do with them. You can't
do unmanaged code in VB.Net, and certain types of control are difficult to
manage with VB.Net. But if you want to develop at a high level, and don't
like or need to get down to the nitty-gritty, and you don't have much
ambition, VB.Net is probably a good language for you.
There are all kinds of programmers in the world. Some of us work at a low
level, and some of us work at a high level. And everywhere in-between. At a
high level, it doesn't matter much. But my job, for example, requires some
fairly low-level stuff, and I like it that way. I'm something of a power
freak when it comes to programming. So, I would not think about going to
VB.Net. But for many people, programming is just a job. They do it for the
money. And for them, the easiest way is the best way.
There was a serious move to C# among VB.Net programmers, and it ended up
muddying the water a bit in terms of hiring. I think anyone wanting to move
back to VB.Net is probably thinking along some very helpful lines for
everyone involved.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.
"Kevin" <ke***@inatrice .co.za> wrote in message
news:11******** *************@f 14g2000cwb.goog legroups.com...I don't know if I should even start this topic but here goes. I'm an ex vb6 developer, now developing in C#. The reason why I started developing in C# is because the company that I worked for at the time standarised on C#.
Many of my friends working in previous companies that I worked for are starting to move back to VB.Net. When I asked them why, it seems that the next release of VB.Net seems very promising and they kinda see themselves in the same position I'm in. It seems that at the time when .Net was first released many companies basically forced developers to work in C# because as in my case the company they worked for standarised on C#, why these companies did this is beyond me because most of their developers were vb developers, I think it's because it was marketed that C# was the main language to use on the .Net Framework.
Now many companies as well as management in these companies are starting to realise that vb.net is not that different from c# and are starting to give their developers a choice and thus obviously the move back to vb.
The reason why I'm posting this topic here is because I'm wondering how many developers using c# are ex vb developers and would actually like to develop in vb.net. I have actually convinced my superiors to use vb.net as another language choice and they have agreed.
We have just started a new project in vb.net about 3 mths ago and I must say that it's still a damn fun language to work in, I'm actually enjoying my work again. Productivity couldn't be higher as other c# (ex vb6) developers in my department have also wanted to go back.
Wondering how many of you out there would like to move back to the lighter side of life?
There are more programmers in the world who cannot afford Visual Studio than
those that can. Command line copiles with notepad as the editor of choice is
surprisingly popular.
C# is a more type-efficient language.
--
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"Kevin" <ke***@inatrice .co.za> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. . Well, I enjoy C# more than I do VB.Net. I originally started development in QBasic then moved to C/C++ on *nix. From there I learned Visual Basic and moved on to the .Net platform and learned VB.Net and C#. I just like C#, the syntax is less wordy (no Then's or End If's), which means less typing... and I really like the way it looks (looks and feels like C/C++).
Mythran
Wow you've been back and forth, QBasic -> C/C++ -> Visual Basic -> C#.
I disagree with your 'less typing' statement in some respect as Then's, End If's and even End Sub End Function are implemented for you as you enter to the next line. Even Catch and Finally is automatically coded for you as you hit enter after a Try statement.
I do agree with your statement about look and feel, this is exactly the point I'm trying to make. I think look and feel is important as it, in my mind, makes you a more productive developer because you feel comfortable with the syntax.
But I can't help wondering if ex vb6 developers now working in C# would be more productive going back to vb.net for this exact same reason. I know I am. This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: dotnetforfood |
last post by:
Joel Spolsky's new article "How Microsoft Lost the API War" at
http://www.joelonsoftware.com/articles/APIWar.html
describes how .NET has failed, how classic VB6 and ASP continue to be
preferred by developers, and how Microsoft has lost control of the
preferred API.
You really should read the article. Here are some excerpts:
<Joel Spolsky>
"And yet, people aren't really using .NET much.
|
by: Fresh Air Rider |
last post by:
Hi
I understand that ASP.net 2.0 (Whidbey) is going to reduce coding by
70%.
Surely this is going to de-skill or dumb down the developer's task and
open up the task of web development to less qualified and trained
staff.
Tell me if I'm wrong.
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
| |
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |