C# and VB.Net?

**Nicholas Paldino [.NET/C# MVP]** · Dec 13 '05, 01:35 PM

Re: C# and VB.Net?

Mantorok,

You really don't need a site to tell you why they are practically equal.
Basically, all of your functionality is going to come from the framework
itself, and nothing that the language provides.

With the exception of unsafe code, there is little, if anything, that C#
offers over VB.NET.

I believe this will change with VB.NET 9.0, however. For your purposes,
though, it doesn't matter, because your people are coming from VB6, and
aren't going to be familiar with the new language features anyway.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard. caspershouse.co m

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=blue]
> Hi all
>
> We are an organisation that use C# currently and we have some members who
> are not yet trained in .Net or C#, some staff have requested they use VB
> instead (probably due to their background).
>
> Given that we are already using C# I think adding VB into the mix is a bad
> idea - not with regards to the language itself but the fact that the
> VB.Net coders won't learn C# and possibly vice-versa.
>
> Apart from the business reasons not to introduce a 2nd .Net language, are
> there any sites with un-biased views as to why both languages are in
> effect - equal?
>
> Thanks
>[/color]

**Mantorok** · Dec 13 '05, 01:45 PM

Re: C# and VB.Net?

"Nicholas Paldino [.NET/C# MVP]" <mvp@spam.guard .caspershouse.c om> wrote in
message news:uU%23aDh%2 3$FHA.984@tk2ms ftngp13.phx.gbl ...[color=blue]
> Mantorok,
>
> You really don't need a site to tell you why they are practically
> equal. Basically, all of your functionality is going to come from the
> framework itself, and nothing that the language provides.
>
> With the exception of unsafe code, there is little, if anything, that
> C# offers over VB.NET.[/color]

Yes - it is preference at the end of the day, our boss wants us to provide
specifics about each languag - which is wrong, it doesn't take a genius to
realise that introducing another language into the mix is going to cause
problems amongst staff.

**Ignacio Machin \( .NET/ C# MVP \)** · Dec 13 '05, 02:05 PM

Re: C# and VB.Net?

Hi,

They are effectively equals as practically all they use are from the
framework, that is common, the only thing that change is the syntax and just
a few other things that normally you can live without.

Having two teams that knows nothing about the other's programming language
is a bad thing though.

IMO, it's lot easier going from C# to VB.NET , I checked this first hand as
I was given a VB.net app to maintain and support like 6 months ago, it was
programmed by a consultant and I'm been updating it since then.

The other way, program C# from VB should not be as trivial though.

Have them learn C# :)

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=blue]
> Hi all
>
> We are an organisation that use C# currently and we have some members who
> are not yet trained in .Net or C#, some staff have requested they use VB
> instead (probably due to their background).
>
> Given that we are already using C# I think adding VB into the mix is a bad
> idea - not with regards to the language itself but the fact that the
> VB.Net coders won't learn C# and possibly vice-versa.
>
> Apart from the business reasons not to introduce a 2nd .Net language, are
> there any sites with un-biased views as to why both languages are in
> effect - equal?
>
> Thanks
>[/color]

**Michael S** · Dec 13 '05, 02:25 PM

Re: C# and VB.Net?

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=blue]
> Hi all
>
> We are an organisation that use C# currently and we have some members who
> are not yet trained in .Net or C#, some staff have requested they use VB
> instead (probably due to their background).
>
> Given that we are already using C# I think adding VB into the mix is a bad
> idea - not with regards to the language itself but the fact that the
> VB.Net coders won't learn C# and possibly vice-versa.
>
> Apart from the business reasons not to introduce a 2nd .Net language, are
> there any sites with un-biased views as to why both languages are in
> effect - equal?
>
> Thanks[/color]

Hi Mantrorok.

As part of my work I train VB6 developers becomming .NET developers. Both
in-house, but we also sell this service to our customers. Hence, I have
trained VBers in both VB.NET and C#, and I have noticed some important
issues with the two languages.

VB6 devs learning C# - pretty soon learns to forget everything they know
about what they used to do, and adopt OO-principles. C# is new and they
think in new directions.

However, the VBers that moves to VB.NET typically have a lot slower
learning-curve. As the syntax is so like the old basic, they tend to think
of VB.NET as just another complex Visual Basic alas more complex.

And the latter group typically don't adopt OO-principles. They still view a
class as some module you just put code and som Dims in, they keep on
concatinating strings, declaring their arrays, and don't get why an
ArrayList or a StringBuilder could ever be useful. The think in terms of
variables and don't get the 'reference on stack, object on heap' model and
can't undestand why passing a huge array to a method would be the bad thing.

Just this monday I visited a customer to do some simple maintainance for
them, and their VB.NET devs still prefix their types like they was variants:
strName, lngAge, objSqlConnectio n. It is so bleeding obvious why they
choosed VB.NET, not becuase they like it, but becuase they liked what they
had. They want to continue coding in same old way as they are used to. I
think most of them are also frustrated with .NET and just think it's complex
and bothersome.

Another thing about VB.NET and OO is the weird syntax, C# maps pretty well
to common concepts in the OO world, while VB.NET is harder to teach:

If I want to make this method abstract do I mark it as abstract?

C# - - Yes.

VB.NET - No Sir! You write mustinherit.

While I hate VB in any form and truly think that Visual Basic Sucks So Hard
It Bends Light -
I tried to give you some real exemples of my experience with teaching .NET
to VBers.

Hope this helped
- Michael S

**Mantorok** · Dec 13 '05, 02:35 PM

Re: C# and VB.Net?

Thanks very much Micael - I think you've hit the nail well and truly on the
head - this is an excellent example to take to my meeting.

"Michael S" <no@mail.com> wrote in message
news:e9R0t%23%2 3$FHA.436@TK2MS FTNGP10.phx.gbl ...[color=blue]
>
> "Mantorok" <none@tiscali.c o.uk> wrote in message
> news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=green]
>> Hi all
>>
>> We are an organisation that use C# currently and we have some members who
>> are not yet trained in .Net or C#, some staff have requested they use VB
>> instead (probably due to their background).
>>
>> Given that we are already using C# I think adding VB into the mix is a
>> bad idea - not with regards to the language itself but the fact that the
>> VB.Net coders won't learn C# and possibly vice-versa.
>>
>> Apart from the business reasons not to introduce a 2nd .Net language, are
>> there any sites with un-biased views as to why both languages are in
>> effect - equal?
>>
>> Thanks[/color]
>
> Hi Mantrorok.
>
> As part of my work I train VB6 developers becomming .NET developers. Both
> in-house, but we also sell this service to our customers. Hence, I have
> trained VBers in both VB.NET and C#, and I have noticed some important
> issues with the two languages.
>
> VB6 devs learning C# - pretty soon learns to forget everything they know
> about what they used to do, and adopt OO-principles. C# is new and they
> think in new directions.
>
> However, the VBers that moves to VB.NET typically have a lot slower
> learning-curve. As the syntax is so like the old basic, they tend to think
> of VB.NET as just another complex Visual Basic alas more complex.
>
> And the latter group typically don't adopt OO-principles. They still view
> a class as some module you just put code and som Dims in, they keep on
> concatinating strings, declaring their arrays, and don't get why an
> ArrayList or a StringBuilder could ever be useful. The think in terms of
> variables and don't get the 'reference on stack, object on heap' model and
> can't undestand why passing a huge array to a method would be the bad
> thing.
>
> Just this monday I visited a customer to do some simple maintainance for
> them, and their VB.NET devs still prefix their types like they was
> variants: strName, lngAge, objSqlConnectio n. It is so bleeding obvious why
> they choosed VB.NET, not becuase they like it, but becuase they liked what
> they had. They want to continue coding in same old way as they are used
> to. I think most of them are also frustrated with .NET and just think it's
> complex and bothersome.
>
> Another thing about VB.NET and OO is the weird syntax, C# maps pretty well
> to common concepts in the OO world, while VB.NET is harder to teach:
>
> If I want to make this method abstract do I mark it as abstract?
>
> C# - - Yes.
>
> VB.NET - No Sir! You write mustinherit.
>
> While I hate VB in any form and truly think that Visual Basic Sucks So
> Hard It Bends Light -
> I tried to give you some real exemples of my experience with teaching .NET
> to VBers.
>
> Hope this helped
> - Michael S
>
>
>[/color]

**Michael S** · Dec 13 '05, 02:45 PM

Re: C# and VB.Net?

No problem, I'll send the invoice. =)

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmlsq$a1h $1@newsfeed.th. ifl.net...[color=blue]
> Thanks very much Micael - I think you've hit the nail well and truly on
> the head - this is an excellent example to take to my meeting.
>
> "Michael S" <no@mail.com> wrote in message
> news:e9R0t%23%2 3$FHA.436@TK2MS FTNGP10.phx.gbl ...[color=green]
>>
>> "Mantorok" <none@tiscali.c o.uk> wrote in message
>> news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=darkred]
>>> Hi all
>>>
>>> We are an organisation that use C# currently and we have some members
>>> who are not yet trained in .Net or C#, some staff have requested they
>>> use VB instead (probably due to their background).
>>>
>>> Given that we are already using C# I think adding VB into the mix is a
>>> bad idea - not with regards to the language itself but the fact that the
>>> VB.Net coders won't learn C# and possibly vice-versa.
>>>
>>> Apart from the business reasons not to introduce a 2nd .Net language,
>>> are there any sites with un-biased views as to why both languages are in
>>> effect - equal?
>>>
>>> Thanks[/color]
>>
>> Hi Mantrorok.
>>
>> As part of my work I train VB6 developers becomming .NET developers. Both
>> in-house, but we also sell this service to our customers. Hence, I have
>> trained VBers in both VB.NET and C#, and I have noticed some important
>> issues with the two languages.
>>
>> VB6 devs learning C# - pretty soon learns to forget everything they know
>> about what they used to do, and adopt OO-principles. C# is new and they
>> think in new directions.
>>
>> However, the VBers that moves to VB.NET typically have a lot slower
>> learning-curve. As the syntax is so like the old basic, they tend to
>> think of VB.NET as just another complex Visual Basic alas more complex.
>>
>> And the latter group typically don't adopt OO-principles. They still view
>> a class as some module you just put code and som Dims in, they keep on
>> concatinating strings, declaring their arrays, and don't get why an
>> ArrayList or a StringBuilder could ever be useful. The think in terms of
>> variables and don't get the 'reference on stack, object on heap' model
>> and can't undestand why passing a huge array to a method would be the bad
>> thing.
>>
>> Just this monday I visited a customer to do some simple maintainance for
>> them, and their VB.NET devs still prefix their types like they was
>> variants: strName, lngAge, objSqlConnectio n. It is so bleeding obvious
>> why they choosed VB.NET, not becuase they like it, but becuase they liked
>> what they had. They want to continue coding in same old way as they are
>> used to. I think most of them are also frustrated with .NET and just
>> think it's complex and bothersome.
>>
>> Another thing about VB.NET and OO is the weird syntax, C# maps pretty
>> well to common concepts in the OO world, while VB.NET is harder to teach:
>>
>> If I want to make this method abstract do I mark it as abstract?
>>
>> C# - - Yes.
>>
>> VB.NET - No Sir! You write mustinherit.
>>
>> While I hate VB in any form and truly think that Visual Basic Sucks So
>> Hard It Bends Light -
>> I tried to give you some real exemples of my experience with teaching
>> .NET to VBers.
>>
>> Hope this helped
>> - Michael S
>>
>>
>>[/color]
>
>[/color]

**Mantorok** · Dec 13 '05, 02:45 PM

Re: C# and VB.Net?

LOL

"Michael S" <no@mail.com> wrote in message
news:umnMxI$$FH A.2736@TK2MSFTN GP11.phx.gbl...[color=blue]
> No problem, I'll send the invoice. =)
>
> "Mantorok" <none@tiscali.c o.uk> wrote in message
> news:dnmlsq$a1h $1@newsfeed.th. ifl.net...[color=green]
>> Thanks very much Micael - I think you've hit the nail well and truly on
>> the head - this is an excellent example to take to my meeting.
>>
>> "Michael S" <no@mail.com> wrote in message
>> news:e9R0t%23%2 3$FHA.436@TK2MS FTNGP10.phx.gbl ...[color=darkred]
>>>
>>> "Mantorok" <none@tiscali.c o.uk> wrote in message
>>> news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...
>>>> Hi all
>>>>
>>>> We are an organisation that use C# currently and we have some members
>>>> who are not yet trained in .Net or C#, some staff have requested they
>>>> use VB instead (probably due to their background).
>>>>
>>>> Given that we are already using C# I think adding VB into the mix is a
>>>> bad idea - not with regards to the language itself but the fact that
>>>> the VB.Net coders won't learn C# and possibly vice-versa.
>>>>
>>>> Apart from the business reasons not to introduce a 2nd .Net language,
>>>> are there any sites with un-biased views as to why both languages are
>>>> in effect - equal?
>>>>
>>>> Thanks
>>>
>>> Hi Mantrorok.
>>>
>>> As part of my work I train VB6 developers becomming .NET developers.
>>> Both in-house, but we also sell this service to our customers. Hence, I
>>> have trained VBers in both VB.NET and C#, and I have noticed some
>>> important issues with the two languages.
>>>
>>> VB6 devs learning C# - pretty soon learns to forget everything they know
>>> about what they used to do, and adopt OO-principles. C# is new and they
>>> think in new directions.
>>>
>>> However, the VBers that moves to VB.NET typically have a lot slower
>>> learning-curve. As the syntax is so like the old basic, they tend to
>>> think of VB.NET as just another complex Visual Basic alas more complex.
>>>
>>> And the latter group typically don't adopt OO-principles. They still
>>> view a class as some module you just put code and som Dims in, they keep
>>> on concatinating strings, declaring their arrays, and don't get why an
>>> ArrayList or a StringBuilder could ever be useful. The think in terms of
>>> variables and don't get the 'reference on stack, object on heap' model
>>> and can't undestand why passing a huge array to a method would be the
>>> bad thing.
>>>
>>> Just this monday I visited a customer to do some simple maintainance for
>>> them, and their VB.NET devs still prefix their types like they was
>>> variants: strName, lngAge, objSqlConnectio n. It is so bleeding obvious
>>> why they choosed VB.NET, not becuase they like it, but becuase they
>>> liked what they had. They want to continue coding in same old way as
>>> they are used to. I think most of them are also frustrated with .NET and
>>> just think it's complex and bothersome.
>>>
>>> Another thing about VB.NET and OO is the weird syntax, C# maps pretty
>>> well to common concepts in the OO world, while VB.NET is harder to
>>> teach:
>>>
>>> If I want to make this method abstract do I mark it as abstract?
>>>
>>> C# - - Yes.
>>>
>>> VB.NET - No Sir! You write mustinherit.
>>>
>>> While I hate VB in any form and truly think that Visual Basic Sucks So
>>> Hard It Bends Light -
>>> I tried to give you some real exemples of my experience with teaching
>>> .NET to VBers.
>>>
>>> Hope this helped
>>> - Michael S
>>>
>>>
>>>[/color]
>>
>>[/color]
>
>[/color]

**Ignacio Machin \( .NET/ C# MVP \)** · Dec 13 '05, 02:55 PM

Re: C# and VB.Net?

Hi,

[color=blue]
> Yes - it is preference at the end of the day, our boss wants us to provide
> specifics about each languag - which is wrong, it doesn't take a genius to
> realise that introducing another language into the mix is going to cause
> problems amongst staff.[/color]

Well, in VB you can have a more relaxed type assignment. which is bad IMO .
string s = theDataTable("C olumn") is acceptable , no need to convert it
to string

Also something that I find incredible that in the 21th century is not
deprecated is the need to place a "_" if you want to write an instruction in
more than one line

**Harry Simpson** · Dec 13 '05, 02:55 PM

Re: C# and VB.Net?

A truly unbiased opinion from someone that can't even get the English
language subject verb agreement thing down.

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmlsq$a1h $1@newsfeed.th. ifl.net...[color=blue]
> Thanks very much Micael - I think you've hit the nail well and truly on
> the head - this is an excellent example to take to my meeting.
>
> "Michael S" <no@mail.com> wrote in message
> news:e9R0t%23%2 3$FHA.436@TK2MS FTNGP10.phx.gbl ...[color=green]
>>
>> "Mantorok" <none@tiscali.c o.uk> wrote in message
>> news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...[color=darkred]
>>> Hi all
>>>
>>> We are an organisation that use C# currently and we have some members
>>> who are not yet trained in .Net or C#, some staff have requested they
>>> use VB instead (probably due to their background).
>>>
>>> Given that we are already using C# I think adding VB into the mix is a
>>> bad idea - not with regards to the language itself but the fact that the
>>> VB.Net coders won't learn C# and possibly vice-versa.
>>>
>>> Apart from the business reasons not to introduce a 2nd .Net language,
>>> are there any sites with un-biased views as to why both languages are in
>>> effect - equal?
>>>
>>> Thanks[/color]
>>
>> Hi Mantrorok.
>>
>> As part of my work I train VB6 developers becomming .NET developers. Both
>> in-house, but we also sell this service to our customers. Hence, I have
>> trained VBers in both VB.NET and C#, and I have noticed some important
>> issues with the two languages.
>>
>> VB6 devs learning C# - pretty soon learns to forget everything they know
>> about what they used to do, and adopt OO-principles. C# is new and they
>> think in new directions.
>>
>> However, the VBers that moves to VB.NET typically have a lot slower
>> learning-curve. As the syntax is so like the old basic, they tend to
>> think of VB.NET as just another complex Visual Basic alas more complex.
>>
>> And the latter group typically don't adopt OO-principles. They still view
>> a class as some module you just put code and som Dims in, they keep on
>> concatinating strings, declaring their arrays, and don't get why an
>> ArrayList or a StringBuilder could ever be useful. The think in terms of
>> variables and don't get the 'reference on stack, object on heap' model
>> and can't undestand why passing a huge array to a method would be the bad
>> thing.
>>
>> Just this monday I visited a customer to do some simple maintainance for
>> them, and their VB.NET devs still prefix their types like they was
>> variants: strName, lngAge, objSqlConnectio n. It is so bleeding obvious
>> why they choosed VB.NET, not becuase they like it, but becuase they liked
>> what they had. They want to continue coding in same old way as they are
>> used to. I think most of them are also frustrated with .NET and just
>> think it's complex and bothersome.
>>
>> Another thing about VB.NET and OO is the weird syntax, C# maps pretty
>> well to common concepts in the OO world, while VB.NET is harder to teach:
>>
>> If I want to make this method abstract do I mark it as abstract?
>>
>> C# - - Yes.
>>
>> VB.NET - No Sir! You write mustinherit.
>>
>> While I hate VB in any form and truly think that Visual Basic Sucks So
>> Hard It Bends Light -
>> I tried to give you some real exemples of my experience with teaching
>> .NET to VBers.
>>
>> Hope this helped
>> - Michael S
>>
>>
>>[/color]
>
>[/color]

**Mantorok** · Dec 13 '05, 03:06 PM

Re: C# and VB.Net?

"Ignacio Machin ( .NET/ C# MVP )" <ignacio.mach in AT dot.state.fl.us > wrote
in message news:e4L1uM$$FH A.2156@TK2MSFTN GP11.phx.gbl...[color=blue]
> Hi,
>
>[color=green]
>> Yes - it is preference at the end of the day, our boss wants us to
>> provide specifics about each languag - which is wrong, it doesn't take a
>> genius to realise that introducing another language into the mix is going
>> to cause problems amongst staff.[/color]
>
>
> Well, in VB you can have a more relaxed type assignment. which is bad IMO
> .
> string s = theDataTable("C olumn") is acceptable , no need to convert it
> to string[/color]

So what happens at runtime if theDataTable("C olumn") is integer? It bombs
presumably?
[color=blue]
> Also something that I find incredible that in the 21th century is not
> deprecated is the need to place a "_" if you want to write an instruction
> in more than one line[/color]

Yep, we had that in FoxPro and I hated it....except it was ; rather than _.

**Michael S** · Dec 13 '05, 03:16 PM

Re: C# and VB.Net?

I would have done much better in Swedish. English is not my first language.
Now go away Troll. There is no food here! Or do you have an opinion youself?

- Michael S

"Harry Simpson" <hssimpson@phgt .net> wrote in message
news:OhrxQP$$FH A.2092@TK2MSFTN GP10.phx.gbl...[color=blue]
>A truly unbiased opinion from someone that can't even get the English
>language subject verb agreement thing down.
>
> "Mantorok" <none@tiscali.c o.uk> wrote in message
> news:dnmlsq$a1h $1@newsfeed.th. ifl.net...[color=green]
>> Thanks very much Micael - I think you've hit the nail well and truly on
>> the head - this is an excellent example to take to my meeting.
>>
>> "Michael S" <no@mail.com> wrote in message
>> news:e9R0t%23%2 3$FHA.436@TK2MS FTNGP10.phx.gbl ...[color=darkred]
>>>
>>> "Mantorok" <none@tiscali.c o.uk> wrote in message
>>> news:dnmhdk$7c8 $1@newsfeed.th. ifl.net...
>>>> Hi all
>>>>
>>>> We are an organisation that use C# currently and we have some members
>>>> who are not yet trained in .Net or C#, some staff have requested they
>>>> use VB instead (probably due to their background).
>>>>
>>>> Given that we are already using C# I think adding VB into the mix is a
>>>> bad idea - not with regards to the language itself but the fact that
>>>> the VB.Net coders won't learn C# and possibly vice-versa.
>>>>
>>>> Apart from the business reasons not to introduce a 2nd .Net language,
>>>> are there any sites with un-biased views as to why both languages are
>>>> in effect - equal?
>>>>
>>>> Thanks
>>>
>>> Hi Mantrorok.
>>>
>>> As part of my work I train VB6 developers becomming .NET developers.
>>> Both in-house, but we also sell this service to our customers. Hence, I
>>> have trained VBers in both VB.NET and C#, and I have noticed some
>>> important issues with the two languages.
>>>
>>> VB6 devs learning C# - pretty soon learns to forget everything they know
>>> about what they used to do, and adopt OO-principles. C# is new and they
>>> think in new directions.
>>>
>>> However, the VBers that moves to VB.NET typically have a lot slower
>>> learning-curve. As the syntax is so like the old basic, they tend to
>>> think of VB.NET as just another complex Visual Basic alas more complex.
>>>
>>> And the latter group typically don't adopt OO-principles. They still
>>> view a class as some module you just put code and som Dims in, they keep
>>> on concatinating strings, declaring their arrays, and don't get why an
>>> ArrayList or a StringBuilder could ever be useful. The think in terms of
>>> variables and don't get the 'reference on stack, object on heap' model
>>> and can't undestand why passing a huge array to a method would be the
>>> bad thing.
>>>
>>> Just this monday I visited a customer to do some simple maintainance for
>>> them, and their VB.NET devs still prefix their types like they was
>>> variants: strName, lngAge, objSqlConnectio n. It is so bleeding obvious
>>> why they choosed VB.NET, not becuase they like it, but becuase they
>>> liked what they had. They want to continue coding in same old way as
>>> they are used to. I think most of them are also frustrated with .NET and
>>> just think it's complex and bothersome.
>>>
>>> Another thing about VB.NET and OO is the weird syntax, C# maps pretty
>>> well to common concepts in the OO world, while VB.NET is harder to
>>> teach:
>>>
>>> If I want to make this method abstract do I mark it as abstract?
>>>
>>> C# - - Yes.
>>>
>>> VB.NET - No Sir! You write mustinherit.
>>>
>>> While I hate VB in any form and truly think that Visual Basic Sucks So
>>> Hard It Bends Light -
>>> I tried to give you some real exemples of my experience with teaching
>>> .NET to VBers.
>>>
>>> Hope this helped
>>> - Michael S
>>>
>>>
>>>[/color]
>>
>>[/color]
>
>[/color]

**philippedoucette@hotmail.com** · Dec 13 '05, 03:16 PM

Re: C# and VB.Net?

I have developed in every version of Microsoft BASIC from the original
ROM chip that shipped with the IBM PC, under every version of DOS and
Windows. Every single one. I finally made the jump to C# and I must
tell you I am so happy. It is true that the OO syntax of C# is true to
the principals of OO so that it will change the way you think when you
program. When I was trying to do OO in VB, I carried with me all my
experience as dead weight and did not do real OO programming. Your
programmers will be better programmers in the long run if they learn
C#. Your code will be more maintainable and you will have a better
product.

**Michael S** · Dec 13 '05, 03:16 PM

Re: C# and VB.Net?

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmn9k$aod $1@newsfeed.th. ifl.net...[color=blue]
>
> "Ignacio Machin ( .NET/ C# MVP )" <ignacio.mach in AT dot.state.fl.us >
> wrote in message news:e4L1uM$$FH A.2156@TK2MSFTN GP11.phx.gbl...[color=green]
>> Hi,
>>
>>[color=darkred]
>>> Yes - it is preference at the end of the day, our boss wants us to
>>> provide specifics about each languag - which is wrong, it doesn't take a
>>> genius to realise that introducing another language into the mix is
>>> going to cause problems amongst staff.[/color]
>>
>>
>> Well, in VB you can have a more relaxed type assignment. which is bad IMO
>> .
>> string s = theDataTable("C olumn") is acceptable , no need to convert it
>> to string[/color]
>
> So what happens at runtime if theDataTable("C olumn") is integer? It bombs
> presumably?
>[color=green]
>> Also something that I find incredible that in the 21th century is not
>> deprecated is the need to place a "_" if you want to write an instruction
>> in more than one line[/color]
>
> Yep, we had that in FoxPro and I hated it....except it was ; rather than
> _.
>[/color]

Those where the days... =)

However, true basic must be in ALL CAPS and use line-numbers. I miss my
C-64.
My first program was on a ABC-80 (In Swedish as I was 8 years old and we are
not taught English until 10):

10 INPUT "WHAT IS YOUR NAME "; X$
20 PRINT "HELLO "; X$

- Michael S

**Ignacio Machin \( .NET/ C# MVP \)** · Dec 13 '05, 03:25 PM

Re: C# and VB.Net?

Hi,

"Mantorok" <none@tiscali.c o.uk> wrote in message
news:dnmn9k$aod $1@newsfeed.th. ifl.net...[color=blue]
>
> "Ignacio Machin ( .NET/ C# MVP )" <ignacio.mach in AT dot.state.fl.us >
> wrote in message news:e4L1uM$$FH A.2156@TK2MSFTN GP11.phx.gbl...[color=green]
>> Hi,
>>
>>[color=darkred]
>>> Yes - it is preference at the end of the day, our boss wants us to
>>> provide specifics about each languag - which is wrong, it doesn't take a
>>> genius to realise that introducing another language into the mix is
>>> going to cause problems amongst staff.[/color]
>>
>>
>> Well, in VB you can have a more relaxed type assignment. which is bad IMO
>> .
>> string s = theDataTable("C olumn") is acceptable , no need to convert it
>> to string[/color]
>
> So what happens at runtime if theDataTable("C olumn") is integer? It bombs
> presumably?[/color]

I Nop, it gets converted in a string, now the opposite (assigning a string
to a integer) throw an exception

cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

C# and VB.Net?

C# and VB.Net?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment