-
MFC vs .Net
What are the disadvantages/advantages to using MFC vs .Net when programming in C++? For developing a potentially commercial application, which do you think is the wiser choice down the line in terms of technological advances, hardware changes, .net changes...etc
-
Re: MFC vs .Net
If you ask me then C# all the way - not that it only offers very rich .Net framework but it also offers much easier way (including the IDE) to develop very complex application.
But question rather falls into C++ vs C# category.
-
Re: MFC vs .Net
It depends a lot on the type of commercial application you're talking about.
For a mass market application or hardware drivers, you'll usually find unmanaged C++ the best approach. Since the development costs and time will be higher, this assumes that you would be getting a sufficient return on investment to program it this way. In this model, support would be a cost center, something to avoid, and the product is essentially standalone.
For vertical/niche market software using C# or VB.NET is usually more cost effective. They can be more rapidly developed and are easier to maintain and customize. This model often assumes a lot of your ROI comes from the software helping to sell your services and support, hardware, or other things. For example, you give the software away or sell it cheaply but to make use of it the customer has to pay $2500 a month in support or web service access fees plus buy/rent your equipment. Support becomes a profit center and the software is essentially a sales tool.