Re: For assembly, C# or VB or C++ ?
- From: " Brooke" <Brooke@xxxxxxxxx>
- Date: Fri, 22 Jul 2005 02:44:16 GMT
I guarantee that C# is just as easy (probably easier since you know C++)
as VB.NET. I have been using VB since it was first released and I was
actually a beta tester for "Thunder" when I lived in Seattle in the early
90's so I am very familiar with VB.
You cannot just jump from VB 6 to VB.NET, you have to take the time to
learn the new syntax, true OOP, and the .NET framework. Since you have to
"learn" VB.NET anyway, why not just make the jump right to C#?
To tell you the truth the two languages are almost exactly the same. If
you learn one you can pickup the other in just a few days. But like I said,
there are millions of lines of C and C++ that you can use in C#. If you have
to make an WIN API call it is very easy coming from a C/C++ background, but
it you are a VB programmer then it is not as easy.
To me there is really no good reason to learn VB.NET. I admit that I
have written and released VB.NET apps, but it was after I learned C#. There
are also more jobs here in Austin, Texas for C# programmers and for some
reason the wages are still higher (just like C++ over VB).
My theory is, "Stick to the three C's" (C, C++, and C#) and you should
always be able to find a decent job. Just about all operating systems can
run the C's apps and most of the embedded programming is done in the first
two "C's".
Bye
"Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F3B3E312-F7EB-4A42-A660-D6DC3C103ED1@xxxxxxxxxxxxxxxx
> Thank you, Brooke.
> Your comments are very much convincing.
> As a C++ programmer, I incline to C# too.
> But, for its simplicity, I am kind of attracted to VB also.
>
> "Brooke" wrote:
>
>> I chose C# because the source code for the .NET platform is in C#. Makes
>> it
>> easy to read the source and better understand what is going on behind the
>> scene.
>>
>> Also, there are millions of lines of C and C++ code out there that can
>> easily be converted to C#. Especially handy when writing code for the
>> Compact Framework as it is missing many features that the desktop version
>> of
>> ..NET has and thus requires making API calls to get the desired
>> functionality.
>>
>>
>>
>> "Daniel O'Connell [C# MVP]" <onyxkirx@xxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:OIOdo9VjFHA.3164@xxxxxxxxxxxxxxxxxxxxxxx
>> >
>> > "Irene" <Irene@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> > news:15CA2FE5-E4D0-4A5C-85C1-963464F69265@xxxxxxxxxxxxxxxx
>> >>I am creating a project, which would have many assemblies in future.
>> >> The question is if I have a choice which language is better to create
>> >> the
>> >> assemblies.
>> >> Or, there is no clear advantages one over another?
>> >
>> > You can mix and match them as you wish, to best suit whatever the
>> > assembly
>> > does.
>> >
>>
>>
>>
.
- Follow-Ups:
- Re: For assembly, C# or VB or C++ ?
- From: Irene
- Re: For assembly, C# or VB or C++ ?
- References:
- For assembly, C# or VB or C++ ?
- From: Irene
- Re: For assembly, C# or VB or C++ ?
- From: Daniel O'Connell [C# MVP]
- Re: For assembly, C# or VB or C++ ?
- From: Brooke
- Re: For assembly, C# or VB or C++ ?
- From: Irene
- For assembly, C# or VB or C++ ?
- Prev by Date: Source Safe
- Next by Date: Re: What to learn?
- Previous by thread: Re: For assembly, C# or VB or C++ ?
- Next by thread: Re: For assembly, C# or VB or C++ ?
- Index(es):
Relevant Pages
|
