Re: Up to date MFC Book
We're starting to use .NET for some smaller applications, but for anything
that needs to be really fast or compact we still have to use C++. I
haven't done much with CLI, but it doesn't look all that different to me.
You are right that C# is probably more .NET focused, but if you already know
C++ then it's nice to have CLI available. And, it's especially nice if you
need to write programs that run partly managned, but use some .NET
interface.
Tom
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:1156862698.697908.279220@74g2000cwt.googlegroups.com...
All this is true to a large extent. But it really depends upon the
code. If code base is large(C++) *and* for whatever reason(I cant think
of any) you want to move to managed world, CLI would make sense. But to
start a new project with C++/CLI makes little sense given how
easy/transparent C# is compared to C++/CLI.
Myself, I really want to ease into .NET by using some subsystem of it
like
the XML reader in my MFC apps. CLI is great for that.
.Net has good support for XML read/write. I think Nish's book on
MFC/.net actually does have sample on this(not that you need it).
---
Ajay