My new session is coming with a title:
Migration path towards Windows Presentation Foundation (WPF) platform – the client inteface of the future
The lecture will be a part of the one-day developer conference organized by Ekobit in Zagreb (Croatia) on October 22 this year.
I will give a lecture with my colleage Dejan Martincevic, who is a professional web developer (MCPD) and also experienced in WPF. Together we will talk about how easy is to migrate to WPF taking several methodologies. Here is the summary of the session, so if you are interested and nearby Zagreb (Croatia), apply for it and join the session!
WPF technology offers us lots of revolutionary features, especially the important role plays XAML language which abstracts visualisation of user interface and experience (UX). As such, XAML becomes a building block not just for desktop apps, but also for web solutions by using Silverlight and other technologies (XPS documents, WF, etc.). It would be perfect if would be possible to begin with the new technology (such as WPF) from the scratch, but we know, it is not always possible – we do not live in the perfect world. This lecture will present exactly this tought – by using best practices of building client applications relying on Windows Forms, make our way for Windows Presentation Foundation platform – the client interface of the future!
What is good to know about the migration
- there is not such thing as a ‘magic wand’ for doing the migration – of course, you can start to write your app from the ground up once again, but this is not an intention of the migration.
- you can host the existing WinForms elements (windows, user controls, third-party and even ActiveX controls) inside a WPF application, as well as to host your WPF elements inside a Windows Forms application.
- there are known issues regarding integration of WinForms via WindowsFormsHost into the WPF layout, such as: sizing, rotating, skewing, proportional scaling, layering (Z-Order), etc., that you should be aware of.
- there is a helper class which you can use for reporting conditions of the browser environment for a WPF application that is hosted by a browser (BrowserInteropHelper).
- there are controls which are not (yet) supported by WPF – MaskedTextBox, ImageList, LinkLabel; dialogs (ColorDialog, FolderBrowserDialog, FontDialog), date controls (DateTimePicker, MonthCalendar), printing controls (PageSetupDialog, PrintDocument, PrintPreviewDialog), and more others…
- some of the controls are drammaticaly or just slightly changed, so you should be aware of all of these…
- there are lots of documentation available on the internet about how to do it.