C# developers going back to vb.net

[Kevin]

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?

[Kevin Spencer]

I taught myself C using a pirated copy of Borland C+ 2.0, which ran on DOS.
I'm not sure what you're referring to, but you should bone up on your
history. Some of us lived through it.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Larry Lard" <la*******@hotm ail.com> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .

Kevin Spencer wrote:
[snip]

C++ is an older implementation/derivation of C. It was designed for very
low-level access, BIOS/processor-level access, in fact. It was developed
prior to the advent of multi-tasking networked operating systems, and
before
it was possible to get yourself into too much trouble with
BIOS/processor-level access.

Thanks for reassuring me that I don't have to set too much store by
things you say.

--
Larry Lard
Replies to group please

[Kevin Spencer]

Yes, Kevin, I actually worked for about 6 years almost exclusively with ASP,
VBScript and VB. I had my own consulting business, and the web database
market was just emerging. In fact, prior to working with ASP, I spent a year
or so working with IDC.

I got very familiar with VBScript and VB, and had no problems with it. I
actually got very comfortable with it, and of course, it was the only RAD
language around. That was its greatest strength. But the advent of the .Net
platform opened up a world of greater possibilities, and I embraced it with
great enthusiasm. In the beginning I worked mainly with VB.Net, as I was in
a primarily ASP/VB shop. But that was about 3 years ago, and I eventually
(after changing jobs) was able to get to the point where I use C# almost
exclusively now. About 99% of the time, that is, except when I have to tweak
some legacy app that is still around here.

--
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******** *************@o 13g2000cwo.goog legroups.com...

Kevin,

One more question, have you ever worked in Visual Basic?
I realised by your reply that you are a very 'c' orientated developer,
you must have been very excited when c# hit the market, this is why I
asked the question whether or not you will be using C++\CLI in the
future. This will give you even more power like deterministic
finalization for instance.

[Kevin Spencer]

Ow. My head hurts.

I have no problems with women of any kind. However, I am married now, so
it's really very moot!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Cor Ligthert [MVP]" <no************ @planet.nl> wrote in message
news:eZ******** ******@tk2msftn gp13.phx.gbl...

Kevin,

Most is agreed by me, however you wrote this.

That means that we make our living by logic.

Logic can be subjective (as you showed), in the way we are handling it
here it has to be in my opinion objective.

Which means that when a choose is because of subject reasons, those
reasons have to be added and be in relation to the object.

(When you are in Holland you will probably be comfortable with woman as
Sally, a lot of nice looking woman here are that tall and you will not
recognize it, so even that subjective part can be important)

:-)

Just my opinion.

Cor

[William Stacey [MVP]]

> Yes, I agree with your statement, but the point I am trying to make is

if people like apples why do they pretend to like oranges because the
majority like oranges and actually they are dying for a nice juicy
apple.

If in fact that was the case. But I see no evidence that people who use c#
are actually dying to use VB instead, nor the reverse. I am sure one can
quote someone here or there on both sides. But my quess would be that most
people are using the language they prefer. That said, if I owned a big
project I would pick one and stick with one. Yes you can use both and let
people choose which one they like, but now you have two different languages
to deal with and people always have to juggle mental conversion even if they
know both. Imagine doing code reviews with two or three different languages
on the table. Have two or more sets of standards, etc, etc. So overall
productivity would suffer I would think. So fact is, some companies need to
make a choice and stick with it.

--
William Stacey [MVP]

[kwkahler]

As many others, in my job I have to go back and forth between C# and VB.NET
quite often. Originally coming from Turbo Pascal I never really found a "true
love" since the DOS days. My opinion is that C# is a cleaner more typesafe
language that in almost all of my projects beats VB.NET in shorter
development cycles and far less bugs. In my opinion C# will be THE language
in the future.
--
William Kahler
..NET Developer, MCSD
"Kevin" wrote:

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?

[Paul]

Get over it Kevin ..... C# is a superior programming language. Embrace change
dude.

"Kevin" wrote:

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?

[Adam Tibi]

Actually, I was a QBasic > VB6 > VB.NET developer and now I had the chance to
switch to C#, I was waiting the chance!!!

* C# syntex is derived from the mother of all languages C++ and that makes
it universal and not a language that only Microsoft developers know! If you
are an ASP.NET developer then you can write JavaScript in a similar way
without adding a "Then" to the "if" (not to mention PHP).
* if you are a common Java and .NET developer, maybe working on both
languages in the same time or migrating from a language to another, you woukd
enjoy C# versus VB.NET.
* C# is "Option Stric On" by default and there is no way to set it off (I'm
addressing lazy developers)
* You type less with C#!
* It is case-sensitive and senior developers might like to have same names
with different case!
* VB.NET bears some bad practices from VB6 like a string variable is empty
string by default, when creating an array you specify the top index versus
the count, etc...
* VB.NET developers that are from VB6 background tends to write code in the
same way they did with VB6 knowing that VB6 is OO based and VB.NET is OOP
language, so they give BAD reputation for the other non-OOB developers!!!

And the list goes on, do I need to say more? I hope I won't be forced to go
back to VB.NET, it sucks!!!

"Kevin" wrote:

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?

[Cor Ligthert [MVP]]

Kevin,

C is almost equal to Unix an OS made especially to let a lot of students use
one computer (multi tasking) at the same time whithout having the change
that happens what students in that situation like to do the most.

http://en.wikipedia.org/wiki/C_%28pr...ng_language%29

:-)

Cor

[Cor Ligthert [MVP]]

Adam,

Do you know Wikipedia, there is a lot stated wrong in your message

http://en.wikipedia.org/wiki/Main_Page
Cor

"Adam Tibi" <Adam Ti**@discussion s.microsoft.com> schreef in bericht
news:87******** *************** ***********@mic rosoft.com...

Actually, I was a QBasic > VB6 > VB.NET developer and now I had the chance
to
switch to C#, I was waiting the chance!!!

* C# syntex is derived from the mother of all languages C++ and that makes
it universal and not a language that only Microsoft developers know! If
you
are an ASP.NET developer then you can write JavaScript in a similar way
without adding a "Then" to the "if" (not to mention PHP).
* if you are a common Java and .NET developer, maybe working on both
languages in the same time or migrating from a language to another, you
woukd
enjoy C# versus VB.NET.
* C# is "Option Stric On" by default and there is no way to set it off
(I'm
addressing lazy developers)
* You type less with C#!
* It is case-sensitive and senior developers might like to have same names
with different case!
* VB.NET bears some bad practices from VB6 like a string variable is empty
string by default, when creating an array you specify the top index versus
the count, etc...
* VB.NET developers that are from VB6 background tends to write code in
the
same way they did with VB6 knowing that VB6 is OO based and VB.NET is OOP
language, so they give BAD reputation for the other non-OOB developers!!!

And the list goes on, do I need to say more? I hope I won't be forced to
go
back to VB.NET, it sucks!!!

"Kevin" wrote:

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?

[Kevin Spencer]

> Do you know Wikipedia, there is a lot stated wrong in your message

Well, Cor, by your own nit-picking standards, your English *sucks*.

http://www.ucl.ac.uk/internet-grammar/home.htm

Get over it, dude. There are more important (and helpful) things to do in
life than nit-pick. If you have a self-image problem, don't compensate. You
will only end up hating yourself even more. If you want to feel good about
yourself, try to make others feel good about themselves. What goes around
comes around.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Big things are made up of
lots of little things.

"Cor Ligthert [MVP]" <no************ @planet.nl> wrote in message
news:uY******** ******@TK2MSFTN GP10.phx.gbl...

Adam,

Do you know Wikipedia, there is a lot stated wrong in your message

http://en.wikipedia.org/wiki/Main_Page
Cor

"Adam Tibi" <Adam Ti**@discussion s.microsoft.com> schreef in bericht
news:87******** *************** ***********@mic rosoft.com...

Actually, I was a QBasic > VB6 > VB.NET developer and now I had the
chance to
switch to C#, I was waiting the chance!!!

* C# syntex is derived from the mother of all languages C++ and that
makes
it universal and not a language that only Microsoft developers know! If
you
are an ASP.NET developer then you can write JavaScript in a similar way
without adding a "Then" to the "if" (not to mention PHP).
* if you are a common Java and .NET developer, maybe working on both
languages in the same time or migrating from a language to another, you
woukd
enjoy C# versus VB.NET.
* C# is "Option Stric On" by default and there is no way to set it off
(I'm
addressing lazy developers)
* You type less with C#!
* It is case-sensitive and senior developers might like to have same
names
with different case!
* VB.NET bears some bad practices from VB6 like a string variable is
empty
string by default, when creating an array you specify the top index
versus
the count, etc...
* VB.NET developers that are from VB6 background tends to write code in
the
same way they did with VB6 knowing that VB6 is OO based and VB.NET is OOP
language, so they give BAD reputation for the other non-OOB developers!!!

And the list goes on, do I need to say more? I hope I won't be forced to
go
back to VB.NET, it sucks!!!

"Kevin" wrote:

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?