As far as I know, the best The way is to use MonoTouch and use C#-Logic as much as possible.
Since the original project was written using WPF for the actual TabletPC, my question is, if there is any way, to reuse WPF sources or at least minimal I have to rewrite the part I have to write again.
If there is any good alternative to MonoTouch, I will also like the hint:)
Update: Your comments are helpful, but Not 100% what I’m looking for. MonoCross looks good, but as far as I know, it just “hides” the iOS-specific parts. I really like that it will be a way to reuse handwritten “special” WPF controls. ( Or at least minimize work/time to transfer them) This would be great.
Update 2: Maybe I should add that I will also accept some “complex” three-step methods. For example, there is Is there no way to convert XAML-WPF files to HTML5 (or something equally powerful) and then use Titanium or PhoneGap? Language and framework shouldn’t be a big issue, I’m just trying to find a way to reuse as much as possible:)
In response to your question, it’s not possible on iPad, iPhone, Reuse WPF Guis on Android. Only Windows Phone supports Silverlight views. To solve this problem, you must use the model view controller architecture (because iOS, Android will not support data binding via MVVM), and create for each architecture Separate view.
Although this may sound laborious, please note that if you structure the application correctly so that the main business logic and presentation logic are placed within the Controller (or service) layer, you can Reuse most of the code. This is the same restriction as the cross-platform code deployed to Silverlight and WPF in both directions on Windows. Xaml files usually have to be specific to each framework, but usually *.cs user controls and view model/code logic can be shared.
Update: After your update (2).
Yes, you can use a third-party server to convert XAML-WPF files to HTML5 – ComponentArt Dashboard Server. This claims to WPF/Silverlight applications written with strict MVVM are converted to HTML5/JS for portability across multiple devices. I cannot guarantee how effective this is, I know it is expensive, but if you are severely stuck, and Hope to transplant WPF -> HTML5 this is worth studying.
Best wishes,
I am trying to convert the existing C#- WPF- Project as an iPad app.
As far as I know, the best way to date is to use MonoTouch and use C#-Logic as much as possible.
The original project was written using WPF for the actual TabletPC, my question is, if there is any way, reuse the WPF source or at least minimize the part that I have to write again.
If there is any good alternative Product MonoTouch, I will also like the prompt:)
Update: Your opinion is helpful, but not 100% of what I am looking for. MonoCross does not look Wrong, but as far as I know, it’s just “hiding” the iOS-specific parts. I really like that it will be a way to reuse handwritten “special” WPF controls. (or at least minimize work/time to transfer them) This will be great.
Update 2: Maybe I should add that I will also accept some “complex” three-step methods. For example, is there a way to convert XAML-WPF files to HTML5( Or something equally powerful), and then use Titanium or PhoneGap? Language and framework shouldn’t be a big issue, I’m just trying to find a way to reuse as much as possible:)
See this previous question which is related, May be interested in creating cross-platform iOS, Android and WP7 applications.
In response to your question, you cannot reuse WPF Guis on iPad, iPhone, Android. Only Windows Phone supports Silverlight view. To solve this problem, you must use the model view controller architecture (because iOS and Android will not support data binding via MVVM) and create a separate view for each architecture.
Although This may sound laborious, but please note that if you structure your application correctly so that you put the main business logic and presentation logic inside the Controller (or service) layer, you can reuse most of the code. This is the same as deploying in both directions on Windows Cross-platform code to Silverlight and WPF are the same restrictions. Xaml files usually have to be specific to each framework, but usually you can share *.cs user controls and view models/code logic.
Update: in your After update (2).
Yes, you can use a third-party server to convert XAML-WPF files to HTML5 – ComponentArt Dashboard Server. This claims to convert WPF/Silverlight applications written using strict MVVM to HTML5/JS for portability across multiple devices. I can’t guarantee how effective this is, I know it is expensive, but if you are severely stuck and want to port WPF -> HTML5 this is worth studying.
Best wishes,