Operational Warfare Developer's Blog

Developer's blog for the Operational Art of War series

About the author

Ralph Trickey maintains TOAW III
I set this Blog up for fun, and for my own edication! Nothing is guaranteed, it's for my own use primarily, so even if I say that something may happen with the next release, please understand that it may not. I plan to post random thoughts and other things like that at random times here. I don't have a specific plan for what will be here.
E-mail me Send mail

Recent posts

Recent comments

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2010

To .Net or not to .Net

Are there any disadvantages to .Net that I'm missing?
I've got a large Native C program (Operational Art of War) that compiles under C, and I'm converting to good Object Oriented code.
It does memory allocation within the audio and video library only. It uses only two third party libraries that I'd have to convert to DLLs.
The port to a nominal C++/CLI program looks like it is pretty trivial.
Converting to .Net has some advantages that I can see.
1) potentially better optimizations for the processor the person is running on
2) the .Net library adds better support for XML, Graphics, etc.
3) the potential to port more easily to other platforms like the XBOX, PDAs, etc.
4) Winforms, or the equivalent, instead of MFC.
5) Marketability of my skills:smoke:
The disadvantages are
1) C++/CLI - I'm not sure how stable this is, MS already tried and dropped managed C++.
2) .Net - It's aready up to 3.5, and there were major changes between 1.1 and 2.0
Right now, I'm leaning towards .Net at a future date, but I'd like to hear other opinions.
Thanks,
Ralph

Posted by Ralph Trickey on Saturday, March 24, 2007 5:20 AM
Permalink | Comments (1) | Post RSSRSS comment feed