Re: Up to date MFC Book
- From: "Ajay Kalra" <ajaykalra@xxxxxxxxx>
- Date: 29 Aug 2006 07:44:58 -0700
It's an open secret that developers are using the move to .NET as an
opportunity to rewrite everything. That was something they'd wanted to do
anyway. This way management will not argue. But converting everything to
.NET is technically not necessary, and there are drawbacks (code
obfuscation, startup speed).
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
.
- Follow-Ups:
- Re: Up to date MFC Book
- From: Tom Serface
- Re: Up to date MFC Book
- From: David Ching
- Re: Up to date MFC Book
- References:
- Up to date MFC Book
- From: AB
- Re: Up to date MFC Book
- From: David Wilkinson
- Re: Up to date MFC Book
- From: Ajay Kalra
- Re: Up to date MFC Book
- From: David Ching
- Up to date MFC Book
- Prev by Date: Re: How to dynamically get the info about the presence of keyboard & mouse
- Next by Date: Re: Displaying Service From Sys Tray
- Previous by thread: Re: Up to date MFC Book
- Next by thread: Re: Up to date MFC Book
- Index(es):
Relevant Pages
|
