2.
Microsoft®

37.
Web desktop Easy to develop and deploy, but limited features and end user experience Rich user experience, often connected, but costly to develop and difficult to deploy Web desktop media & RIA

38.
Design Develop Deploy

39.
Flexible tools / programming / media Compelling UX on all app categories Connected to data, servers, services Media & RIA Desktop Web XHTML / ASP.NET JavaScript / AJAX CSS .NET Languages XAML / WPF Windows Media

40.
Who uses Silverlight? Content Providers Engage visitors with highest quality interactive web sites, video and game experiences with lower costs Designers / Developers Role-specific suite of tools for designers and developers using existing skills and domain knowledge and building on existing application investments Viewers / End Users Sites “light up” equally on Windows and Mac, with a one-time, fast install (~2MB)

41.
Silverlight Momentum By the Numbers 26 months since launch Silverlight first shipped in 2007…

42.
Silverlight Momentum By the Numbers 26 months since launch 500m+ downloads 500m+

43.
Silverlight Momentum By the Numbers Source: Microsoft Developer Tracker 2008 Report 26 months since launch 500m+ downloads 500,000+ Developers & Designers 500,000+

44.
Silverlight Momentum By the Numbers 26 months since launch 500m+ downloads 500,000+ Developers & Designers 350+ partners in 30 countries

45.
Silverlight Momentum By the Numbers 26 months since launch 500m+ downloads 500,000+ Developers & Designers 350+ partners in 30 countries 350+ Microsoft Products & Websites

46.
Silverlight Momentum By the Numbers www.silverlight.net/showcase 26 months since launch 500m+ downloads 500,000+ Developers & Designers 350+ partners in 30 countries 350+ Microsoft Products & Websites Thousands of Apps across the world

58.
Why Silverlight?

59.
Why Silverlight? Low Cost, High Quality Media Compelling, Cross-Platform User Experiences Flexible Programming Model with Collaboration Tools Low Cost, High Quality Media Connected to Data, Servers, and Services

60.
Why Silverlight? Compelling, Cross-Platform User Experiences Flexible Programming Model with Collaboration Tools Low Cost, High Quality Media Connected to Data, Servers, and Services

61.
Why Silverlight? Flexible Programming Model with Collaboration Tools Compelling, Cross-Platform User Experiences Low Cost, High Quality Media Connected to Data, Servers, and Services

62.
Why Silverlight? Connected to Data, Servers, and Services Compelling, Cross-Platform User Experiences Flexible Programming Model with Collaboration Tools Low Cost, High Quality Media

63.
What Can Silverlight Brings To Business Application? <ul><li>The deployment is easy – applications are delivered over the Web or via the web browser </li></ul><ul><li>Very small runtime is required </li></ul><ul><li>Can be written in your favorite .NET language (C#, Visual Basic, etc.) </li></ul><ul><li>Can run in multiple platforms </li></ul><ul><li>Faster to develop and richer than HTML-based applications </li></ul>

64.
SL versus WPF <ul><li>Shared features: </li></ul><ul><li>Both use XAML for defining user interfaces (with Silverlight essentially a subset of WPF). </li></ul><ul><li>Both can be deployed via a browser as sandboxed applications. </li></ul>

65.
SL versus WPF <ul><li>Pros: </li></ul><ul><li>WPF has minimal restrictions, and it requires no sandbox (unless deployed via a browser as an XBAP without full trust turned on). </li></ul><ul><li>WPF has the power of the full .NET Framework behind it. </li></ul>

66.
SL versus WPF <ul><li>Cons: </li></ul><ul><li>WPF requires the full .NET Framework to be installed on the machine. </li></ul><ul><li>WPF is limited to running on Windows only. </li></ul><ul><li>WPF does not have the hype and community/Microsoft support that Silverlight has. </li></ul>

67.
SL versus WinForms <ul><li>Shared features: </li></ul><ul><li>Both can be downloaded via a browser (although Windows Forms applications cannot be run within the browser like Silverlight applications) and update themselves automatically when a new version is available (using click-once with Windows Forms applications). </li></ul>

68.
SL versus WinForms <ul><li>Pros: </li></ul><ul><li>Windows Forms has minimal restrictions and no sandbox. </li></ul><ul><li>has the power of the full .NET Framework behind it.; easy to develop (no need to understand XAML). </li></ul><ul><li>mature, having been around since the inception of the .NET Framework. </li></ul><ul><li>requires no graphical skills to design user interfaces with the standard style of Windows applications. </li></ul>

69.
SL versus WinForms <ul><li>Cons: </li></ul><ul><li>requires the full .NET Framework to be installed on the machine. </li></ul><ul><li>limited to running on Windows only. </li></ul><ul><li>an aging platform with waning support. </li></ul><ul><li>Data binding capabilities aren’t as rich. </li></ul><ul><li>User interfaces aren’t as flexible and don’t have the same styling capabilities. </li></ul>

70.
SL versus WinForms <ul><li>Create unique each flexible UI – support for data binding, vector graphics, animations, etc. </li></ul><ul><li>Makes designing applications clean and easy </li></ul><ul><li>Can share code/s with WP7 and WPF applications </li></ul><ul><li>Setup your runtime and application faster </li></ul>

71.
SL versus HTML Based Applications <ul><li>Renders exactly the same way in each browser or operating system </li></ul><ul><li>Richer, faster to develop </li></ul><ul><li>No constant postbacks </li></ul><ul><li>No need to write in JavaScript </li></ul><ul><li>Can be run offline </li></ul><ul><li>Can be run as standard application </li></ul>

72.
SL versus ASP.NET <ul><li>Shared features: </li></ul><ul><li>Both ASP.NET and Silverlight are available via a web browser (for Silverlight applications, the Silverlight plug-in must be installed first). </li></ul>

73.
SL versus ASP.NET <ul><li>Pros: </li></ul><ul><li>runs on almost all Internet-connected devices. </li></ul><ul><li>does not require a plug-in to be installed. </li></ul><ul><li>It has the power of the full .NET Framework behind it (server side only). </li></ul><ul><li>mature, having been around since the inception of the .NET Framework. </li></ul>

74.
SL versus ASP.NET <ul><li>Cons: </li></ul><ul><li>requires the full .NET Framework to be installed on a Windows server running IIS (although the Mono project provides a potential alternative). </li></ul><ul><li>Client-side code must be written in JavaScript, requiring learning a different language. </li></ul><ul><li>can render differently between browsers, requiring a lot of testing. </li></ul>

75.
SL versus ASP.NET <ul><li>Cons: </li></ul><ul><li>Data binding capabilities aren’t as rich. </li></ul><ul><li>Not as rich or responsive (although Ajax and jQuery can help) </li></ul><ul><li>cannot run with elevated trust to integrate with other software and hardware. </li></ul>

76.
SL versus Adobe Flash/Flex <ul><li>Similar features: </li></ul><ul><li>Both are rich Internet application platforms deployed via a web browser. </li></ul><ul><li>Both can run applications outside of the browser (Silverlight with no additional requirements, Flash with Adobe Air). </li></ul><ul><li>Both use XML-based markup languages to define their user interfaces. </li></ul>

77.
SL versus Adobe Flash/Flex <ul><li>Pros: </li></ul><ul><li>The Flash runtime is almost ubiquitous, installed on almost all Internet-capable PCs. </li></ul><ul><li>The core Flash runtime is a smaller download (1.8MB vs. 6MB), although running outside the browser requires the Adobe Air runtime (which is 15MB). </li></ul>

78.
SL versus Adobe Flash/Flex <ul><li>Cons: </li></ul><ul><li>Code must be written using ActionScript, a JavaScript derivative, which is not as capable or popular as managed code languages (e.g., there’s no equivalent to LINQ and generics), and is specific to Flash/Flex (i.e., code can’t be reused with other applications). </li></ul>

79.
SL versus Adobe Flash/Flex <ul><li>Cons: </li></ul><ul><li>It requires an additional download to run applications outside the browser (Adobe Air), and applications must be packaged separately to run in this runtime (whereas the same Silverlight application will run both within and outside the browser). </li></ul>

80.
Disadvantages of SL <ul><li>Over HTML-based applications </li></ul><ul><li>Reach of users in HTML </li></ul><ul><li>Plug-in requirement </li></ul><ul><li>Over WinForms </li></ul><ul><li>Subset of .NET framework </li></ul><ul><li>Not designed for integrating with other applications, OS, or hardware devices* </li></ul>

81.
Considerations in using SL <ul><li>Determine the current and potential future requirements of your application. </li></ul><ul><li>Identify any feature that conflicts with SL’s limitations </li></ul><ul><li>Do not choose a technology because it’s ‘cool’.* </li></ul><ul><li>SL is not a perfect platform </li></ul>

82.
Support for Higher Quality Video and Audio Media Webcam and Microphone Native Multicast Output Protection Online and Offline Content Protection H.264 Content Protection Developer Tools Beyond the Browser Business Applications Rich Experiences Media Local Recording

83.
Empowering Rich Experiences Rich Experiences Developer Tools Beyond the Browser Business Applications Rich Experiences Media Fluid User Interface Copy and Paste Drag and Drop Productivity Enhancements Google Chrome Support Enhanced Performance

84.
Business Applications Business Applications Developer Tools Beyond the Browser Business Applications Rich Experiences Media Printing Forms Controls WCF RIA Services Enhanced Data binding Internationalization Managed Extensibility Framework

85.
Silverlight 4 New Capabilities : Beyond the Browser Beyond the Browser Beyond the Browser Developer Tools Beyond the Browser Business Applications Rich Experiences Media Trusted Applications Render HTML within Silverlight Notifications Local File System Access Applications and Devices Cross Domain Access

86.
Developer Tools World Class tooling for development and design Developer Tools Beyond the Browser Business Applications Rich Experiences Media Silverlight Support Design Surface Drag and Drop Data Binding XAML Intellisense Import Blend Resources Sketchflow

87.
Required Tools <ul><li>Visual Studio 2008/2010 </li></ul><ul><li>Expression Blend 4 and SketchFlow </li></ul><ul><li>Silverlight 4 Tools </li></ul><ul><li>WCF RIA Services* </li></ul><ul><li>Silverlight Toolkit </li></ul><ul><li>SQL Server 2008 </li></ul><ul><li>Silverlight Spy (and .NET reflector)* </li></ul>

88.
Exercise #1: My First Silverlight Application

89.
Exercise #2: Creating an OOB application

90.
Exercise #3: Adding a Notification Window

91.
Exercise #4: Hosting an HTML content in Silverlight

92.
Exercise #5: Using ComInterop With Office

93.
Exercise #6: Using BingMap Control

94.
Exercise #7: Publishing Pivots

95.
Exercise #8: Working with Charts

96.
Exercise #8: Printing in Silverlight

97.
Exercise #9: Using Full Screen Mode

98.
Exercise #10: Using Animations, Behaviors, etc.

99.
Exercise #11: My First Silverlight Business Application

100.
Exercise #12: Validation, Binding, DataForm and DataGrid

101.
Abram John A. Limpin http://abramlimpin.com

105.
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.