Is .Net/C# supposed to supplant MFC/c++ on the desktop?

[Shelly]

Hi All,
I'm a long time MFC programmer, but I do more UI than network programming.

Is C# the way to go for non-networked windows desktop apps, is MFC still
the way to go, or is something else brewing?

Thanks,

-Shelly

[Brad Williams]

I think it is pretty obvious that .NET is the future of Windows systems.
But I think the question of whether to rely on the Framework for a new
Windows app *today* boils down to a main issue: Who are your customers and
how feasible is it to require the Framework (and therefore possibly
installation of it) on their machine for your app?

A parallel point is that MFC skills are well on their way to becoming niche.
Already I would not want to be looking for work as a Windows developer with
no .NET experience, it could be a brutal experience. The market is changing
very quickly.

Brad Williams
"Shelly" <Shell@gas..> wrote in message
news:kx*******************@fe12.usenetserver.com.. .

Hi All,
I'm a long time MFC programmer, but I do more UI than network programming.

Is C# the way to go for non-networked windows desktop apps, is MFC still
the way to go, or is something else brewing?

Thanks,

-Shelly

[anonymous]

pardon my french, but mfc is one of the most poorly
designed pieces of merd microsoft ever published.

c#/ dotnet on the other hand is possibly the best product
ms has ever designed, windows, word and all others
included.

-----Original Message-----
Hi All,
I'm a long time MFC programmer, but I do more UI than network programming.
Is C# the way to go for non-networked windows desktop apps, is MFC stillthe way to go, or is something else brewing?

Thanks,

-Shelly

.