From: Giovanni Dicanio on
"Ajay Kalra" <ajaykalra(a)> ha scritto nel messaggio

> MSFT didnt need VB.Net. C# was enough.

To my knowledge, the only thing that VB.NET could do better than C# was
managing COM late-binding (i.e. IDispatch) in a programmer's friendly way.

This could be come in handy when automating Microsoft Office.
This blog post clearly shows the advantage of using VB.NET vs. C# in that
particular scenario:

"Back to Basics: var != Dim"

However, in .NET 4 the features of VB.NET and C# were aligned together, and
my understanding is that now C# supports COM late-binding in a much better
(and programmer's friendly) way.


From: Ajay Kalra on
On Feb 23, 3:15 am, "Mihai N." <nmihai_year_2...(a)> wrote:
> > I would have really expected it to go the other way, especially with
> > the advent of .Net.
> If one care at least a little bit about cross-platoform,
> then .NET is out of the picture instantly.

Very likely but so is MFC. I wasnt comparing one way or the other. I
was simply pointing out the way market is shaping and has been for a

From: Ajay Kalra on
On Feb 23, 8:07 am, Cholo Lennon <chololen...(a)> wrote:
> Ajay Kalra wrote:
> > On Feb 22, 5:36 pm, Joseph M. Newcomer <newco...(a)> wrote:
> >> Microsoft VB developers were once numbered 2,000,000 compared to VC++ 700,000.
> > This is how I remember it. Although numbers I had was 700K vs
> > 1.4million. Regdless, it was clearly VB over C++.
> This is confusing... Are we talking about VC++ or C++? It's not the same
> thing...

Certainly. I am certain this is Visual vs Visual comparison; all on
MSFT's platform.

From: Tom Serface on
I thought the same as Hector about C# until I started using it. There are
just so many things in it's favor:

1. The IDE works much nicer with it.
2. I only does Unicode so no stupid macros for strings.
3. I don't have to prototype functions.
4. When I make changes to the names of controls, all of the references are
updated automatically.
5. The syntax is very simple to learn and use.
6. I get the same MSIL as I do with C++.

I am a huge C++ fan, as you know, but I can certainly understand why most
people would use C# for .NET programming.


"Giovanni Dicanio" <giovanniDOTdicanio(a)> wrote in message
> "Hector Santos" <sant9442(a)> ha scritto nel messaggio
> news:ePsgBdHtKHA.732(a)TK2MSFTNGP06.phx.gbl...
>> The CLI is common to all .NET languages so its just a different high
>> level language. I personally find C# an awkward language.
> I think that for a programmer with C/C++/Java background, the C# syntax
> seems more natural than the VB.NET syntax (at least, this is my feeling).
> Giovanni
From: Tom Serface on
I'd love to see a metric showing how VC++ fares among all of the C++
compilers, but I haven't seen anything like that. I suspect there are lot
of Linux and Mac users not using VC++ (although some will use it when doing
cross platform dev with frameworks like QT).

I don't think the numbers were a good indication for VC++, but they did lend
credibility to C++ as a still popular language. I would guess that would
mean if someone were cross platforming to Windows they would likely at least
try C++ as their first choice language if they were already using it
elsewhere. That means an investment in making C++ more attractive could pay
off if Microsoft can attract server and desktop user to Microsoft platforms.

Like the guy from Monty Python says, we're "not quite dead yet".


"Joseph M. Newcomer" <newcomer(a)> wrote in message
> For the 2M vs 700K, it was VB vs. VC++.
> For the overall popularity of C++ over all other languages, it is all C++
> (including gcc,
> Microsoft's VC++, Intel's C++, etc.) compilers vs. all other languages
> from all other
> vendors.
> joe

First  |  Prev  |  Next  |  Last
Pages: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Prev: CMenu class and menu object
Next: need some class help