Looking for Opinions: .NET/MFC

[japhy]

Hi:

I have a rather large program written using Visual C++ 6.0. It is a dialog-based MFC application.

I've made the switch to Visual C++ .NET 2003 now, and would like some opinions on the following predicament:

I would like to use some third-party NET Winform objects...an Iocomp Software produced plot pack and a Graphics Server Technologies produced plot pack. My options are 1) to figure out a way to drop these objects into an MFC application and access their built-in functions OR 2) rewrite my entire application as a Windows Form application.

I'd appreciate any input I can get about which you all think is a better option.
Thanks...

 

[xwb]

There is a third option - get the Beta of Visual Studio 2005 and rewrite as an Avalon application.

1) How quickly do you need to finish it. If you need to finish it quickly, pick the system that most developers are familiar with.
2) Are the developers more familiar with Windows Forms or MFC? Are they so familiar with MFC that they are pissed off with it and would like to learn something new like Windows Forms? New stuff is a great way of retaining staff.
3) If you don't have experience of either, try Avalon - it is new, (more like web based forms in that it is self adjusting) and you and your team will be more marketable.
4) Can you get the sources for the third party stuff? If you have to move to XP 64-bit, can the libraries be rebuilt for that platform? What is the shelf life of the product? If it is 2 years then you don't have to worry about XP64. If it is more than that then you probably do.

A lot of this is just management decisions. Once you've made up your mind on which direction you want to go, you can move forward.