Sample Code - VB or C#?

[Chad Z. Hower aka Kudzu]

I need to provide a series of demos for an assembly. There are potentialy
several dozen of them. None of them are very complex, however maintaining two
versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving
forward, time just does not permit. So I have to choose - C# or VB? For me,
it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users
can read VB code easily than VB users can easily read C# code.

However if I choose VB, I might alienate C# users. My feeling here is that C#
users generally can read VB, but hold a general disdain for it and feel
somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither
one.

Comments? Suggestions? Corrections?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Cor]

Hi Kudzu,

My expirience in this newsgroup is different than you say.

It should be, but it is not.

When I contribute samples in another more general newsgroup for Adonet and I
do it in VB than I recognize that C# users often do not understand that is
almost exactly the same.
(I try to put in those samples as less declaration and casting as posible
and than mostly the only extra difference is the ";" the () and [] )

The same expirience I have here in this newstgroup with VB users about C#
when Herfried supports a link to a C# sample.

I hope this helps you?

Cor

[Chad Z. Hower aka Kudzu]

"Cor" <no*@non.com> wrote in news:us**************@TK2MSFTNGP10.phx.gbl:

When I contribute samples in another more general newsgroup for Adonet
and I do it in VB than I recognize that C# users often do not understand
that is almost exactly the same.
What kind of reactions do you get from C# users though?
The same expirience I have here in this newstgroup with VB users about
C# when Herfried supports a link to a C# sample.
What kind of reaction do VB developers have when people post C# code here?
I hope this helps you?

Kind of - Im not sure what the reactions of your users were. :)
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Herfried K. Wagner [MVP]]

Chad,

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

I need to provide a series of demos for an assembly. There are potentialy
several dozen of them. None of them are very complex, however maintaining two
versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving
forward, time just does not permit. So I have to choose - C# or VB? For me,
it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users
can read VB code easily than VB users can easily read C# code.
I don't think so. I often read in C# groups and C#ies more often don't
/want/ to read VB.NET code ("bah, it's BASIC") while VB.NET programmers
more often will read C# code in order to solve a problem.
However if I choose VB, I might alienate C# users. My feeling here is that C#
users generally can read VB, but hold a general disdain for it and feel
somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither
one.

Comments? Suggestions? Corrections?

Look for a coworker who will help you to provide the samples in both
programming languages.

:-)

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Cor]

Hi Kudzu,

I think the answer is already given by Herfried, I think I had written the
same on this answer.

But feel free to ask you know?

Cor

[Jay B. Harlow [MVP - Outlook]]

Chad,
I would not worry about alienating one group over the other personally per
se.

Some of the very basic ones I have provided in both C# and VB. However moving forward, time just does not permit. So I have to choose - C# or VB? For me, it does not really matter. I am comfortable in either one. Why not choose both?

Do the simply ones in both as you said, and then do some advanced ones in C#
& some advanced ones in VB.NET, with a more or less equal representation?

Another alternative, what is the language of the assembly itself? Favor that
language?

Hope this helps
Jay

"Chad Z. Hower aka Kudzu" <cp**@hower.org> wrote in message
news:Xn*****************@127.0.0.1... I need to provide a series of demos for an assembly. There are potentialy
several dozen of them. None of them are very complex, however maintaining two versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving forward, time just does not permit. So I have to choose - C# or VB? For me, it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users can read VB code easily than VB users can easily read C# code.

However if I choose VB, I might alienate C# users. My feeling here is that C# users generally can read VB, but hold a general disdain for it and feel
somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither one.

Comments? Suggestions? Corrections?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Jay B. Harlow [MVP - Outlook]]

Herfried,

I don't think so. I often read in C# groups and C#ies more often don't
/want/ to read VB.NET code ("bah, it's BASIC") while VB.NET programmers
more often will read C# code in order to solve a problem.
That's where I will use "Here's a VB.NET sample, if you need help converting
let me know" ;-)

If the sample is not simply enough to be quickly converted.

Then again I am a firm believer in you should be able to READ & both
languages.

Jay

"Herfried K. Wagner [MVP]" <hi***************@gmx.at> wrote in message
news:eb**************@TK2MSFTNGP09.phx.gbl... Chad,

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

I need to provide a series of demos for an assembly. There are potentialy several dozen of them. None of them are very complex, however maintaining two versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving forward, time just does not permit. So I have to choose - C# or VB? For me, it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users can read VB code easily than VB users can easily read C# code.

I don't think so. I often read in C# groups and C#ies more often don't
/want/ to read VB.NET code ("bah, it's BASIC") while VB.NET programmers
more often will read C# code in order to solve a problem.

However if I choose VB, I might alienate C# users. My feeling here is that C# users generally can read VB, but hold a general disdain for it and feel
somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither one.

Comments? Suggestions? Corrections?

Look for a coworker who will help you to provide the samples in both
programming languages.

:-)

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Chad Z. Hower aka Kudzu]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in
news:eb**************@TK2MSFTNGP09.phx.gbl:

I don't think so. I often read in C# groups and C#ies more often don't
/want/ to read VB.NET code ("bah, it's BASIC") while VB.NET programmers
Yes, that the problem. C#ites dont want to read VB code. :) Either way I wil
alienate some, but which one will be "offended" less? :)
Look for a coworker who will help you to provide the samples in both
programming languages.

Its a matter of time - we already have 12 people, and enough work schedule to
fill all their time for a LONG time to come. :)
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:e9**************@tk2msftngp13.phx.gbl:

Do the simply ones in both as you said, and then do some advanced ones
in C# & some advanced ones in VB.NET, with a more or less equal
representation?
Possible, but Id prefer to be consistent. Im leaning towards C#, with some VB
ports where time permits.
Another alternative, what is the language of the assembly itself? Favor
that language?

Delphi. :)

I already have sample code for all of that.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Cor]

Hi Chad,

I should advice you to think about to write it in the language which is in
your idea the farest from Delphi

Delphi. :)

This sounds strange, but mostly people start to copy as much as possible
from the old language and bringing than aspects in the samples which are
from the previous language.

You see it still in some of the VB.net samples on MSDN (although it becomes
better and better) those look sometimes as just rewritten C++ samples. A
language has also an own style in describing things and I think that is also
important.

Cor

[Chad Z. Hower aka Kudzu]

"Cor" <no*@non.com> wrote in news:ea**************@TK2MSFTNGP11.phx.gbl:

This sounds strange, but mostly people start to copy as much as possible
from the old language and bringing than aspects in the samples which are
from the previous language.

Ive done a lot of C++ as well as VB, so that wont be a big problem.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Herfried K. Wagner [MVP]]

Chad,

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

I don't think so. I often read in C# groups and C#ies more often don't
/want/ to read VB.NET code ("bah, it's BASIC") while VB.NET programmers

Yes, that the problem. C#ites dont want to read VB code. :) Either way I wil
alienate some, but which one will be "offended" less? :)

If you ask this question in a VB.NET group, you'll get the answer that
you should write the samples in VB.NET. In the C# group people will
tell you that they would prefer samples written in C#. It's a very hard
decision.

Look for a coworker who will help you to provide the samples in both
programming languages.

Its a matter of time - we already have 12 people, and enough work schedule to
fill all their time for a LONG time to come. :)

Mhm...

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

Another alternative, what is the language of the assembly itself? Favor
that language?

Delphi. :)

Delphi .NET?

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Chad Z. Hower aka Kudzu]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in
news:#v**************@TK2MSFTNGP10.phx.gbl:

If you ask this question in a VB.NET group, you'll get the answer that
you should write the samples in VB.NET. In the C# group people will
Ive asked on both groups, and not as a cross post so I dont start a flame
war.
tell you that they would prefer samples written in C#. It's a very hard
decision.

Yes of course. But I can measure the reactions of each group relating to
disgust of reading the other language. :)

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in
news:OR**************@TK2MSFTNGP12.phx.gbl:

Delphi .NET?

Yes of course. Delphi 8. Its actually code that compiles in Delphi.Net as
well as Delphi 5-7, Kylix (Linux), and C++ Builder 5-6.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Herfried K. Wagner [MVP]]

Chad,

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

If you ask this question in a VB.NET group, you'll get the answer that
you should write the samples in VB.NET. In the C# group people will

Ive asked on both groups, and not as a cross post so I dont start a flame
war.

Very clever...

tell you that they would prefer samples written in C#. It's a very hard
decision.

Yes of course. But I can measure the reactions of each group relating to
disgust of reading the other language. :)

Would be interesting if you let us know about your final decision!

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

Delphi .NET?

Yes of course. Delphi 8. Its actually code that compiles in Delphi.Net as
well as Delphi 5-7, Kylix (Linux), and C++ Builder 5-6.

I wonder that there are any people using Delphi for .NET development...

;-)

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Markus Hahn]

Maybe this helps you: from my own experience, I switched from C# to
Visual Basic.NET a couple of weeks ago (a mixture of curiosity and
looking back to the old VB3 days). There were many new things I learned
what this new BASIC dialect can do and also knowing C# I'm not so sure
if someone one familiar with the sharp language can read VB.NET
instantly. Depends on the complexity, I guess - but some things
(modules, with, chr, ctype) could make the understanding harder. If it's
only .NET Framework API calls then I guess you're fine with any
language. On the other hand VB.NET programmers probably will choke on
expressions like "while (null != (test = (obj = new
Foo()).Items[nI++]));" . Tough question indeed...

-markus

"Chad Z. Hower aka Kudzu" <cp**@hower.org> wrote in message
news:Xn*****************@127.0.0.1...

I need to provide a series of demos for an assembly. There are potentialy several dozen of them. None of them are very complex, however maintaining two versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving forward, time just does not permit. So I have to choose - C# or VB? For me, it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users can read VB code easily than VB users can easily read C# code.

However if I choose VB, I might alienate C# users. My feeling here is that C# users generally can read VB, but hold a general disdain for it and feel somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither one.

Comments? Suggestions? Corrections?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in news:OLbj
$d**********@TK2MSFTNGP12.phx.gbl:

I wonder that there are any people using Delphi for .NET development...

Plenty. Without starting a flamewar - Delphi.net does not require a near
rewrite of your existing code like VB.net and C# users have had to do.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

"Markus Hahn" <ma*********@gmx.net> wrote in news:c1USb.4915$F23.395
@newsread2.news.pas.earthlink.net:

language. On the other hand VB.NET programmers probably will choke on
expressions like "while (null != (test = (obj = new
Foo()).Items[nI++]));" . Tough question indeed...

I'll be sure to not include anything cryptic - but there are uses of using.
Like this:

using (FileStream LOutput = new FileStream(@"c:\temp\test.txt",
FileMode.Create))
{
.....
}

Should most VB'ers be able to understand this?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

hi***************@gmx.at (Herfried K. Wagner [MVP]) wrote in news:O#
3M************@TK2MSFTNGP09.phx.gbl:

Yes of course. But I can measure the reactions of each group relating to
disgust of reading the other language. :)

Would be interesting if you let us know about your final decision!

Gladly. Here is what I have put into the documentation regarding sample code.

Examples

Providing all examples in all languages creates a maintenance nightmare and
detracts from time that would otherwise be dedicated to content. While Indy
supports Delphi, C++, C#, Visual Basic and J#, example code will be provided
as follows:

C# and Delphi - All sample code is provided in both C# and Delphi.
Visual Basic - Limited sample code is provided in Visual Basic. When Visual
Basic code is not available, the C# source should be referred to.
J# - No J# examples are provided. J# developers should refer to the C# code.
C++ - No sample code is provided in C++. C++ Builder developers should refer
to the Delphi code.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Herfried K. Wagner [MVP]]

Chad,

* "Chad Z. Hower aka Kudzu" <cp**@hower.org> scripsit:

I wonder that there are any people using Delphi for .NET development...

Plenty. Without starting a flamewar - Delphi.net does not require a near
rewrite of your existing code like VB.net and C# users have had to do.

That's indeed a very big advantage...

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Herfried K. Wagner [MVP]]

* "Markus Hahn" <ma*********@gmx.net> scripsit:

language. On the other hand VB.NET programmers probably will choke on
expressions like "while (null != (test = (obj = new
Foo()).Items[nI++]));" . Tough question indeed...

'for' has a different (misleading) meaning in C#.

'using' doesn't exist in VB.NET (at the moment).

Indexers are different in VB.NET and C#.

Calling the base class's ctor is different.

'continue' doesn't exist in VB.NET at the moment (this will make
conversion C# -> VB.NET harder).

The event model is different.

....

--
Herfried K. Wagner [MVP]
<http://www.mvps.org/dotnet>

[Rob Windsor [MVP]]

Hey Chad,

So, another Delphi guy makes the switch ;-) I used to help run the Toronto
Delphi User Group, I've attended a couple of your talks.

Anyway, from what I've seen developers are starting to realize that it's the
framework that matters, not the syntax you use to make calls to it. There
are three .NET groups in or near Toronto and speakers use whatever language
they are comfortable with when they present. I run the local VB group and
we've had afew presenters show C# sample code. I've done a few talks at the
Delphi group using VB.NET, C# with VS, C# with C# Builder and Delphi for
..NET and the message about the technology still gets across. It'll take a
while longer before you won't get any complaints but it won't be that long.

I think the main reason people want to see code in the language they use is
so when they download your samples after the presentation they can cut and
paste instead of translate.

Just my $0.02 CAN.

--
Rob Windsor [MVP-VB]
G6 Consulting
Toronto, Canada

"Chad Z. Hower aka Kudzu" <cp**@hower.org> wrote in message
news:Xn*****************@127.0.0.1...

I need to provide a series of demos for an assembly. There are potentialy
several dozen of them. None of them are very complex, however maintaining two versions of them will be very maintainance intensive.

Some of the very basic ones I have provided in both C# and VB. However moving forward, time just does not permit. So I have to choose - C# or VB? For me, it does not really matter. I am comfortable in either one.

If I choose C#, this will alienate VB users. My feeling is that more C# users can read VB code easily than VB users can easily read C# code.

However if I choose VB, I might alienate C# users. My feeling here is that C# users generally can read VB, but hold a general disdain for it and feel
somewhat slighted if they have to read VB and no C# is available.

I would like to equally include both communities with a preference to neither one.

Comments? Suggestions? Corrections?
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

"Rob Windsor [MVP]" <rw******@NO.MORE.SPAM.bigfoot.com> wrote in
news:#l**************@tk2msftngp13.phx.gbl:

So, another Delphi guy makes the switch ;-) I used to help run the
I wouldnt call it a switch. :)

Im still using Delphi a LOT. I just have to show C# and VB users how to use
assemblies produced in Delphi.
Toronto Delphi User Group, I've attended a couple of your talks.
Great. :)
language they are comfortable with when they present. I run the local VB
group and we've had afew presenters show C# sample code. I've done a few
talks at the Delphi group using VB.NET, C# with VS, C# with C# Builder

Great. But C# programmers still look down on VB - and probably will for a
long time. Many of them are prior C++ developers.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Jay B. Harlow [MVP - Outlook]]

Chad,

Possible, but Id prefer to be consistent. Im leaning towards C#, with some VB ports where time permits. Samples in both is consistent in my book! Favoring one over the other is
inconsistent in my book!

Look at how MSDN does it, they provide samples in C#, VB.NET, Managed C++
and J#.

Any less would really be a disservice to your potential customers!

Consider the word Compromise!

As you have suggested. If you do only C#, I suspect you will alienate VB.NET
programmers, if you do only VB.NET you will alienate C# programmers, seeing
as complete examples in both may not be doable by yourself, I am suggesting
some of each to minimize alienating C# or VB.NET developers. Of course then
you risk alienating J# & Managed C++ developers.

A fair compromise is an equal number of samples in each, if complete samples
in both are not readily doable.

Hope this helps
Jay


"Chad Z. Hower aka Kudzu" <cp**@hower.org> wrote in message
news:Xn******************@127.0.0.1... "Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:e9**************@tk2msftngp13.phx.gbl:

Do the simply ones in both as you said, and then do some advanced ones
in C# & some advanced ones in VB.NET, with a more or less equal
representation?
Possible, but Id prefer to be consistent. Im leaning towards C#, with some

VB ports where time permits.

Another alternative, what is the language of the assembly itself? Favor
that language?

Delphi. :)

I already have sample code for all of that.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Cor]

Hi Rob,

Same as I alway say the languages are only the glue.

Cor

Anyway, from what I've seen developers are starting to realize that it's the framework that matters, not the syntax you use to make calls to it.

[Chad Z. Hower aka Kudzu]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:ut**************@TK2MSFTNGP11.phx.gbl:

Look at how MSDN does it, they provide samples in C#, VB.NET, Managed
C++ and J#.

Any less would really be a disservice to your potential customers!
If there were only enough hours in day...

Microsoft has what thousands, if not tens of thousands of people?
VB.NET developers. Of course then you risk alienating J# & Managed C++
developers.

Im not very concerned about them because:

a) J# is a joke and there are very few people actually using it. Those that
are are plenty used to reading C#.

b) Managed C++ - Arent a whole lot of them either. Most of them are C++
diehards who are just resisting the move to C#. They are used to reading C#
too.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Jay B. Harlow [MVP - Outlook]]

Chad,

Microsoft has what thousands, if not tens of thousands of people? Is your project is the same scope as .NET? Are you implying that you would
need thousands of people to create samples for your project? If you do, then
that is all the more reason to do the samples in every language!

However I get the impression you are missing the point I am trying to make.

If you need 6 examples, do 6 examples: 3 in C# and 3 in VB.NET. Surely you
can handle doing 3 in each.

There is no need for a response. As I am dropping out of this discussion.

Note have you considered asking developers in these newsgroups to help
create examples, rather then "alienating" them by suggesting you can only
create samples in a single language?

Again good luck, I'm out of this discussion.

Hope this helps
Jay

"Chad Z. Hower aka Kudzu" <cp**@hower.org> wrote in message
news:Xn******************@127.0.0.1... "Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:ut**************@TK2MSFTNGP11.phx.gbl:

Look at how MSDN does it, they provide samples in C#, VB.NET, Managed
C++ and J#.

Any less would really be a disservice to your potential customers!
If there were only enough hours in day...

Microsoft has what thousands, if not tens of thousands of people?

VB.NET developers. Of course then you risk alienating J# & Managed C++
developers.

Im not very concerned about them because:

a) J# is a joke and there are very few people actually using it. Those

that are are plenty used to reading C#.

b) Managed C++ - Arent a whole lot of them either. Most of them are C++
diehards who are just resisting the move to C#. They are used to reading C# too.

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:#I**************@TK2MSFTNGP10.phx.gbl:

If you need 6 examples, do 6 examples: 3 in C# and 3 in VB.NET. Surely
you can handle doing 3 in each.
We are going to do some in VB, and some ports. But the majority will be C#.
The samples are quite varied in purpose.
Note have you considered asking developers in these newsgroups to help
create examples, rather then "alienating" them by suggesting you can
only create samples in a single language?

Kind of - for the Indy demos yes, we have created a team. However these
samples are for a semi-commercial purpose and I doubt users would want to
work for free for that. :)
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com

[Chad Z. Hower aka Kudzu]

"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in
news:#I**************@TK2MSFTNGP10.phx.gbl:

If you need 6 examples, do 6 examples: 3 in C# and 3 in VB.NET. Surely
you can handle doing 3 in each.
We are going to do some in VB, and some ports. But the majority will be C#.
The samples are quite varied in purpose.
Note have you considered asking developers in these newsgroups to help
create examples, rather then "alienating" them by suggesting you can
only create samples in a single language?

Kind of - for the Indy demos yes, we have created a team. However these
samples are for a semi-commercial purpose and I doubt users would want to
work for free for that. :)
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"
ELKNews - Get your free copy at http://www.atozedsoftware.com