.NET Framework installed base - Making a business decision
Posted on 2004-04-08
We're at a point in the development of our application where we're considering the costs of maintaining and trying to market our geriatric looking MFC application, versus migrating to .NET and an updated interface. The primary question that comes in to play is the .NET Framework. We realize that with the next release of Windows, the .NET Framework will be pre-installed, but coming from a web development background, I am well aware of users' tendency to linger with old software when newer solutions are available. I'm afraid of the number of users out there who don't have the framework installed.
This leads to the core of my question. Just how many people actually have the .NET Framework already? Some people I have talked to already seem to think it's a moot point because you can just include the .NET Framework with your distrubution, but the framework is an additional 23 megabytes and adds a step to the installation process. I don't have to argue about users' attention spans; we all know they're short.
I know a hard number will be nearly impossible to come by, so I'm hoping to hear from some .NET developers who have a product in the marketplace. Are there any examples of .NET applications from major companies (>1 million annual revenue)? I hate to be a follower, but we're a small company with a limited market and I can't afford to take the un-beaten path. How has your experience with selling and supporting a .NET application been? Would you recommend it?
Thanks for any information or experiences you can share. Don't hesitate to post any information you have, regardless of how small or large your user base may be. I'm interested in it all.