Charles Craig
Top achievements
Rank 1
Rank 1
Charles Craig
asked on 21 Apr 2008, 08:59 PM
Is it possible to integrate your WinForm controls within a new WPF application?
Cheers
Chuck
Cheers
Chuck
4 Answers, 1 is accepted
0
Hello Charles Craig,
Theoretically it is possible to use the telerik RadControls for Windows form in an WPF application, using a pair of container controls, formerly codenamed Crossbow. However, using this interoperability components will not be as easy as developing a WPF-only application. Migration may be another issue in this case.
Concerning this, we currently developing a WPF suite of components. It expected to be rolled out in the Q2 2008 release. Of course, there will be a couple of preview releases for the convenience of those interested in integrating these tools in an application sooner.
You can find more information about this here:
http://blogs.telerik.com/HristoKosev/Posts/06-11-09/r_a_d_controls_for_WinForms_in_WPF.aspx
Greetings,
Mike
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Theoretically it is possible to use the telerik RadControls for Windows form in an WPF application, using a pair of container controls, formerly codenamed Crossbow. However, using this interoperability components will not be as easy as developing a WPF-only application. Migration may be another issue in this case.
Concerning this, we currently developing a WPF suite of components. It expected to be rolled out in the Q2 2008 release. Of course, there will be a couple of preview releases for the convenience of those interested in integrating these tools in an application sooner.
You can find more information about this here:
http://blogs.telerik.com/HristoKosev/Posts/06-11-09/r_a_d_controls_for_WinForms_in_WPF.aspx
Greetings,
Mike
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Accepted
Charles Craig
Top achievements
Rank 1
Rank 1
answered on 22 Apr 2008, 01:09 PM
Thanks for the quick response, I'll review the provided link.
Cheers
Chuck
Cheers
Chuck
0
Mirec
Top achievements
Rank 1
Rank 1
answered on 01 May 2008, 09:26 PM
Hi, I'm currently strongly speculating about telerik components as a great way to build our new application framework. I would like to ask in reply to previous question some importat things.
As I understand, there will be new set of RAD controls for WPF.
So when I decide today to start developing with RAD controls for WinForms would be possible to simple migrate to WPF set?
What will be it cost to migrate WinForms controls to your WPF controls?
I'm new here. I had read that you have own presentation framework (TPF). So, this TPF should be abstraction layer above physical presentation layer like WinForms or WPF. Am I right?
If I'm right then there should be simple replacement/migration like replacing only references to assemblies...
What strategy do you have.
Thanks for your soon answer.
Yours sincerely
Miroslav Galajda
As I understand, there will be new set of RAD controls for WPF.
So when I decide today to start developing with RAD controls for WinForms would be possible to simple migrate to WPF set?
What will be it cost to migrate WinForms controls to your WPF controls?
I'm new here. I had read that you have own presentation framework (TPF). So, this TPF should be abstraction layer above physical presentation layer like WinForms or WPF. Am I right?
If I'm right then there should be simple replacement/migration like replacing only references to assemblies...
What strategy do you have.
Thanks for your soon answer.
Yours sincerely
Miroslav Galajda
0
Hello Miroslav,
We are using our own Telerik presentation framework as a basis of our winforms control suite. This presentation framework is not an abstraction layer for WPF, because our controls work under .NET Framework 2.0. It nevertheless uses several of the ideas, introduced with WPF, but it is a pure WinForms framework.
I cannot speculate on the cost of migration in your particular case, as it depends on the complexity and nature of the application. For example, our WPF suite may lack the counterpart controls that we offer in the WInForms suite, or vice versa. Theming and visual appearance, although similar, will also be an issue, because WinForms and WPF controls are skinned differently. In other words, migrating a WinForms application to WPF will entail more than just changing assembly references. The TPF will make things harder, because the concepts we use are already included in WPF. Honestly speaking, I am not sure that migrating from our WinForms controls to the WPF controls will be easy. More on the topic you can find here: Have a safe trip from WinForms to WPF.
I would suggest taking another path - chose one of the technologies and stick to it. If you are thinking of using WinForms and then migrating to WPF, this would take nearly twice the effort compared to going with WPF from the very start. WinForms is not dead yet and it is still the recommended technology for LOB applications.
The technology that you are going to use depends solely on your resources and requirements. Do you have a requirement to use WinForms or WPF? Is your team competence heavier in favor of WinForms? Is something preventing you from considering WPF as an implementation platform at this point? Is the application business oriented, i.e. will it use data controls, such as grids, treeviews, etc? Will it use themes, animations, or other visual goodies? The answers to these questions will help you decide which technology to use. Here are a couple of readings which will help you with this decision:
Sincerely yours, Vassil
Instantly find answers to your questions at the new Telerik Support Center
We are using our own Telerik presentation framework as a basis of our winforms control suite. This presentation framework is not an abstraction layer for WPF, because our controls work under .NET Framework 2.0. It nevertheless uses several of the ideas, introduced with WPF, but it is a pure WinForms framework.
I cannot speculate on the cost of migration in your particular case, as it depends on the complexity and nature of the application. For example, our WPF suite may lack the counterpart controls that we offer in the WInForms suite, or vice versa. Theming and visual appearance, although similar, will also be an issue, because WinForms and WPF controls are skinned differently. In other words, migrating a WinForms application to WPF will entail more than just changing assembly references. The TPF will make things harder, because the concepts we use are already included in WPF. Honestly speaking, I am not sure that migrating from our WinForms controls to the WPF controls will be easy. More on the topic you can find here: Have a safe trip from WinForms to WPF.
I would suggest taking another path - chose one of the technologies and stick to it. If you are thinking of using WinForms and then migrating to WPF, this would take nearly twice the effort compared to going with WPF from the very start. WinForms is not dead yet and it is still the recommended technology for LOB applications.
The technology that you are going to use depends solely on your resources and requirements. Do you have a requirement to use WinForms or WPF? Is your team competence heavier in favor of WinForms? Is something preventing you from considering WPF as an implementation platform at this point? Is the application business oriented, i.e. will it use data controls, such as grids, treeviews, etc? Will it use themes, animations, or other visual goodies? The answers to these questions will help you decide which technology to use. Here are a couple of readings which will help you with this decision:
- Whitepaper: Deciding When To Adopt Windows Presentation Foundation
- Silverlight, WPF, Windows Forms, Ajax - Which One is for Me?
- WPF or WinForms, choose wisely
Sincerely yours, Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center