This document discusses migrating applications from Windows Forms to WPF/Silverlight, highlighting reasons for migration, technology choices, and architectural considerations. It emphasizes WPF's suitability for desktop applications requiring deeper system integration, while Silverlight is easier for beginners and web applications. The author also reviews project organization, testing practices, and the importance of security in development.

1. From legacy to WPF/SLMigrating applications from Windows Form to WPF/SilverlightRaffaele Garofalo

2. Who am I?Raffaele GarofaloNET Software ArchitectMCP (MCAD, MCSD, MCTS)Blog: http://blog.raffaeu.comTwitter: @raffaeuCompany: Nephila Capital Ltd. (www.nephila.com) I am Italian, sorry for my bad English

3. My BooksMicrosoftAPRESS

4. SummaryReasons for migratingChoose the right technologyIs Windows Form dead?Choose the right architectureThe teamSome useful tools

5. Reasons for migratingLegacy application that requires refactoring (partial)Legacy application developed with a very old technology (FoxPro, VB6, …) (re-write)Application that requires a more complex UI (User Interface) not sustainable with Windows Form (partial)Specific request from the Customer (at the end, he has the money …)New project (never start a new project with an old technology!)

6. Always consider the budget!You do not need to re-write everything, you can keep the existing UI and migrate only the new featuresWindows Form can live in parallel with WPF/SLYou can host Windows Form in WPF (WindowsFormHost) and WPF in Windows Form (ElementHost) or SL in Windows Form (embed browser)

7. Is Windows Form dead?No, it is not. There are still thousands of active projects done in Windows FormWin Form is still the following step after VB6 WPF is not intended to replace Windows FormsIt is not dead but it is an old technology. It is still available It does not separate UI from code, I can’t employ a designer for the UI

8. Choose the right technologyFirst rule: WPF is for Standalone, Silverlight is for Web, PhonesSecond rule: WPF works only on Windows OS, Silverlight works on Windows, MAC, LinuxThird rule: WPF is a more powerful technology, Silverlight uses a restricted version of the NET Framework but more feasible for Web and MediaWPF requires a knowledge of XAML for WPF, Silverlight requires XAML for SL, HTML and JS and WCF

9. What can I do with?WPFFull .NET Framework(i.e. Split() has 6 overrides)UI objects derives from Visual base classRouted events, more controlCryptography more powerfulNot a lot of choices for Media managementSILVERLIGHTRestricted version of .NET(i.e. Split() has 3 overrides)UI objects derives from ControlRouted events, less controlSL supports only 4 hash algorithmsGreat support to Media management and streaming

10. What Microsoft suggests? SLIf you're just starting out, and there's a question as to which technology to choose (Silverlight or WPF) then start with Silverlight. It is generally easier to move up to WPF from Silverlight than it is to move the other way. Silverlight has a smaller API, and is therefore generally considered easier to learn.If you need a desktop application with only basic system integration, consider building a Silverlight Out-of-Browser application. Silverlight 4 Trusted Applications with IDispatch support provide access to many system resources previously unavailable to web technologies.If you need deep system integration, excellent multi-touch support, device access, local resources, and all the other things that go with a solid desktop application, then consider moving up to WPF.If you're a C++ developer, you can choose to go with C++ and MFC, or use C++ with WPF on the front end, like the Expression team did.

11. Still missing …WPFA good designer tool, VS is not cool as BlendThe Control toolkit is not exhaustive, you still need a third party control librarySilverlightSame thingInteraction with HTML and Javascript still lacks in some partsStill requires to recompile your .dlls

12. Composite FrameworksCreate an application using Modules (independent assemblies)Specialize teams in different areas (UI, Presentation, Business)Reusable architectureIncrease quality and usability by sharing common services and functionality

13. Composite for WPF/SLPrismRequires observer patterns (message broker)Cool navigation service in V4Only IoC with Unity (Microsoft)Astonishing resources and documentationcaliburnAuto-wiringTransitions between ViewsOpen source with less technology limitsAvailable also for Windows Phone

14. DemoWinForm demo application (MSDN, Telerik)WPF demo application (MSDN, Codeplex)Silverlight demo application (MSDN, Telerik)WPF showcasehttp://windowsclient.net/community/showcase.aspxSilverlight showcasehttp://www.silverlight.net/showcase/

15. Choose the right architectureLayered application or monolithic block?SOA or not SOA? If I work with Silverlight that’s the only choice …TDD or not TDD?What about an O/RM? Entity Framework, Nhibernate or what?What about security, especially if I am working with SL?Design patterns, is M-V-VM mandatory?

16. Layered application, why?Why should I use a layered application if it requires:More codeMore timeMore effortMore peopleMore money

17. Layered application, why?The application we are designing is complex or it will be complex in the futureI need to be able to make my application scalable, maintainable and secureI want to split the project over multiple teams and resourcesI need to recycle as many code/features as I canI need to cover with test as much surface as I can

18. Layered applications

19. SOA (Service Oriented Architecture)Real reasonsWe need to hide the datastore and the business logicI need to spread the business logic over different technologies (WPF, Phones, REST)I can’t migrate everything (like AS400 …) so I need a bridge between old/newDeveloper’s reasonsI need to get certified on WCFIt is cool and I am the only one that doesn’t use it yetI can write 10 times more code to do the same thing

20. TDD Overview

21. TDD Overview. A good unit test …Run fast (they have short setups, run times, and break downs).Run in isolation (you should be able to reorder them).Use data that makes them easy to read and to understand.Use real data (e.g. copies of production data) when they need to.Represent one step towards your overall goal.

22. TDD Pros and ConsPROSIndicator of project’s healthLess time to fix bugsYou should write application using functional codeGood documentation for you code by function/requirementsCONSOne change may requires more effort on fixing tests than fixing real codeTime to write testsYou may not always need to write applications using functional codeWrong test will document wrong requirement

23. O/RM, which one?Nhibernate, Entity Framework are free, others are notNhibernate is 100% flexible but no IDEEF has an IDE but is not flexibleNhibernate has years and is open sourceEF is still not mature and it is not open sourceNhibernate requires more experience, it is not for newbie

24. O/RMPROSYou are not anymore Database technology drivenWrite applications faster, do not need ton of SQLEasier to test the data layerCONSLess flexibility because you can’t use all the power of a specific RDBMSDevs tend to forget T-SQL/PL-SQLThe database become a simple container of data, no more logic in it

25. Security real facts, did you know?Most developers have no clue about securityMost of the intranet applications are not secure at all, especially WinFormSOA implies an additional layer of securityThe database should also be encryptedA web application with “secret” data should be always SSLThe NET framework provides tons of utilities and facilities to apply security

26. Security concerns for my applicationAuthentication, how the user will authenticate against the applicationAuthentication with SOAAuthorization, are we applying also granular security rights?Logging, do we know what is going on? Do we have a trace?Data protection, is security applied also at the data tier or do we use SA in SQL?

27. M-V-VM Overview

28. M-V-VM Main conceptsProvides separation of concernsIt is natural pattern for XAML platformsEnables the developer-designer workflowIncreases application testability

29. Resources on M-V-VMIn the Box Visual Studio integration (SEE DEMO)My BookGary McLean’s bookPRISM documentationhttp://compositewpf.codeplex.com/Josh Smith http://joshsmithonwpf.wordpress.com/Karl Shiffletthttp://karlshifflett.wordpress.com/

30. The TeamHow big is the team I will work with?How much experience do they have?Guru | Some exp. | newbieWhat was their previous project? Do they know the difference between Client (WPF) and Web (SL)?Is there a technology leader in the Team with some experience?

31. The right oneNever put too many seniors: “Too many cooks spoil the dinner”Never use big teams, lot of technical debates and few hours on writing code Put together devs that love the technology they are working with, negativity is a cancerTools make a developer life easier (documentation, books, controls, …)

32. Make your life easierChoose a set of Controls, learn it and use it! Apply one pattern for the UI, learn it and use it. Do not “experiment” with customer money, do what you know and avoid the unknownDo not over engineer, remember that the Customer can appreciate only what he can see … (a.k.a. no NASA web services)Small steps, small releases, small iterations

33. Some toolsBooksGuidanceBest practicesForums and Communities

34. BooksMy book Architecting Applications for the EnterprisePRISM’s Developer Guide (MS PRESS)WPF 4 Unleashed (Adam Nathan)Silverlight 4 Unleashed (L. Bugnion)

35. GuidanceCodeplexhttp://wpfslguidance.codeplex.com/MSDN“Developers Guide to Microsoft PRISM”WPFhttp://windowsclient.netSilverlighthttp://silverlight.net

36. QA?