Raffaele will provide a gap analysis and the potential problems or advantages of moving from a Win32 technology to a vectorial technology like WPF/Silverlight. A detailed discussion and samples will be provided to address when to use WPF and when to use Silverlight.
Topics that we will analyze in this workshop:Why we want to migrate an application? Do we really need to?Why we should use one technology instead of another one? Silverlight, WPF, what else?Is Windows Form dead? What about SL?Why we should choose one design instead of another one? Should I use an O/RM, shouldn’t I? Should I use SOA, shouldn’t I?Is my team ready for a new technology? If it’s not ready, what should I do?Some useful tools and links
Who I am, what is my experience and my backgroundHow you can reach me, what I write in my blogWhere I work, what do I do thereDifferences between software developer and architect
Why two different booksWhat do I talk about in the microsoft book?LayeringDesign patternsDALDDDTDDBLLMVVMWhat in the second one?WPFLayeringBlendEntity FrameworkWCFStylesDataTemplate
Topics that we will analyze in this workshop:Why we want to migrate an application? Do we really need to?Why we should use one technology instead of another one? Silverlight, WPF, what else?Is Windows Form dead? What about SL?Why we should choose one design instead of another one? Should I use an O/RM, shouldn’t I? Should I use SOA, shouldn’t I?Is my team ready for a new technology? If it’s not ready, what should I do?Some useful tools and links
I have a legacy application in Windows Form and I do not have the time to migrate or change itso it would be easier to add an additional component or module in WPF/SL and leave the old application as isI have a very old application that can’t be kept alive as is, so I need to re-write itThe technology I am using, like Windows Form, has some big limits and I can’t go over these limitsThe Customer wants an application using a new technology because it will guarantee a more durable lifeWhy should I use an old technology with a new project?
Remember that the budget if fundamental. I can’t invest 6 months for an application that is already working just because I want to move into a new technology. The customer will not understand this business decision. I need to provide a real reason.Microsoft has designed WPF and SL and Windows Form in a way that the compatibility will be kept alive. This was the first target and this is the reason there isn’t an official tool to migrate from Win Form to WPF. You simply do not need it!
There are tons of active projects written in Windows Form, in C++ and of course Microsoft can’t get rid of sucha technology in one shotRemember about VB6 to NET 2003If you were working with VBx before, Win Form is the natural next move. Same IDE, same way of handling methods, eventsJust more OOPIt is not dead but it won’t work forever. Consider what happened to Windows Phone. Windows CE 6 is not dead but the new phones will work on WP7 (Silverlight)Windows Form runs on Windows 7 but rumors say that in the future only WPF and SL will run on the next versions of Windows (they are rumors)At the PDC 2010 Microsoft didn’t talk at all about Windows Form. Guess why?It is an old technology and if you move to WPF you will have tons of advantages, right away
Standalone means that it runs on a Client, it doesn’t need necessarily a web connection andit doesn’t need a browser and so on … Less security implied because it doesn’t use the internet. Less portable …SL is designed for the web and WP7 for the phones. SO different technology for different audience!WPF is a Windows technology while Silverlight is cross platform, cross device but with some limitationsWPF is more powerful but Silverlight is more feasible for Web and MediaWPF is for core developers, Silverlight is for web developers because it is a web technology
Some demo with Windows Form. The UI loads slower because it takes more timeSome demo with WPF, better UI but more CPU usageSome silvelright demo, good but on IE they looks different than in chromeSHOW INSTALL SL LOCALLYSHOW WPF and SL showcases
Should I stick the code inside the WPF view or should I use a layered architectureWhen it is the case of working with SOA, when it is not the caseTest Driven is a waste of time or it is notWhat are the advantages of using an O/RM and why we should use itWhat are the considerations about security that I should do especially with Silverlight and SOAAre design patterns mandatory?