Bright Future for Winforms?
-
I'm always nervous about the new technology becoming the next VB6. So what is the future for a new app being developed with Winforms and C#? I can see a long upgrade path for this product and I have no interest in making a radical UI change anytime soon. Sure, I know about WPF, but the timing isn't right for my use of that platform.
-
I'm always nervous about the new technology becoming the next VB6. So what is the future for a new app being developed with Winforms and C#? I can see a long upgrade path for this product and I have no interest in making a radical UI change anytime soon. Sure, I know about WPF, but the timing isn't right for my use of that platform.
Well, VB6 was around for a fair while, and so has Winforms now been. If you don't want to use WPF then WinForms is the only real option apart from C++/MFC ( which is kind of dead ). WPF is what will replace WinForms.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
Well, VB6 was around for a fair while, and so has Winforms now been. If you don't want to use WPF then WinForms is the only real option apart from C++/MFC ( which is kind of dead ). WPF is what will replace WinForms.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
Thanks Christian. I'm already a C++/MFC guy and the choice is pretty confusing right now! I guess I'll follow my new found interest.
-
I'm always nervous about the new technology becoming the next VB6. So what is the future for a new app being developed with Winforms and C#? I can see a long upgrade path for this product and I have no interest in making a radical UI change anytime soon. Sure, I know about WPF, but the timing isn't right for my use of that platform.
Well, your best bet is to have good separation between business logic and presentation. Then if GUI technology evolves hopefully you'll have minimal work.
Kevin
-
I'm always nervous about the new technology becoming the next VB6. So what is the future for a new app being developed with Winforms and C#? I can see a long upgrade path for this product and I have no interest in making a radical UI change anytime soon. Sure, I know about WPF, but the timing isn't right for my use of that platform.
Windows Forms will be around for a long time, since it is an integral part of the .NET Framework. That being said, there are no new innovations planned for the WinForms technology as the new, preferred UI platform is WPF. The drawback to WPF right now is that the tools aren't available yet to make development as easy as it is for WinForms. The other concern for WPF is that it isn't yet applicable to every application. There are some things that are just better done in WinForms right now. The best approach is to separate the business logic and the UI as much as possible. This will allow you to gradually migrate to WPF from WinForms when it makes sense. Also, you can combine WinForms and WPF in the same application, with a few technical limitations on the interop.
----------------------------- In just two days, tomorrow will be yesterday.