Re: #if !defined(AFX_

The only reason for using C++ for .NET that I can see, and I'm a pretty huge
C++ fan, is if you need to do managed and unmanaged and don't want to dink
around with using C# for part of it and C++ for another part of it.

I think the direction for C++ is starting to be revealed in threads like
this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1032378&SiteID=1

That said, you can use WPF with C++, it is just not as easy as with C# since
you don't get the WPF Designer.

http://msdn2.microsoft.com/en-us/library/ms742522.aspx

I think the new strategy for C++ makes a lot of sense. It is not difficult
for me, as a C++ programmer, to switch between C++ and C# (I do it daily
several times) so there is room in my life for both. I don't see our native
programs going away for a long time (we need fast servers for controlling
media devices), but we use C# with ASP.NET for controlling the servers.
It's always been my contention that it makes sense to use the best tool for
the job and Windows programmers need to understand more than one tool. I
don't think this is anything new. Used to be we knew VB & C++. Now we know
..NET and C++.

Tom

"Giovanni Dicanio" <giovanni.dicanio@invalid.it> wrote in message
news:u%23qengi$HHA.3548@TK2MSFTNGP06.phx.gbl...