Silverlight Overview

Short Description
Silverlight 1.1 will contain a substantial subset of the .NET 3.5 runtime (also running cross-browser and cross-platform) and will enable a new generation of smart/rich internet applications. Silverlight 1.1 has the potential to become an ASP.NET or even an HTML application killer, especially where sophisticated, feature-rich applications are involved. Silverlight will essentially host a full .NET runtime engine within a sandbox on the client computer and allow a .NET smart client application to run on any platform, all with the same deployment characteristics as a thin-client application (once the Silverlight plug-in has been installed). Essentially, Silverlight creates a “best of both worlds” environment, in which users can experience responsive, media-rich internet applications that leverage local computing power and resources, while administrators enjoy the benefits of ?notouch ? deployments and centralized control.

Website: www.devforce.com.au | Filesize: 39kb
No of Page(s): 3

Content
Silverlight Adoption Curve
Just like any browser plug-in, Silverlight will face an initial adoption curve, and the value of the plug-in as a target platform for development will be determined by the number of end-user installations. However, given the excitement over the powerful capabilities of Silverlight, the speed of a Silverlight download (20 seconds over broadband), and Microsoft?s vast distribution channel (Microsoft will likely include it in every Internet Explorer and Windows installation as well as on every new PC), Silverlight adoption will likely proceed at a brisk pace and reach high levels of market penetration quickly.
ASP.NET Migration to Silverlight
Once the Silverlight plug-in has gained market acceptance, ASP.NET application architects are likely to ask why they should prefer development in ASP.NET rather than Silverlight. On the one hand, they could write a ?Web 2.0? application using AJAX, JavaScript, HTML, CSS, and a back-end programming language, with the necessity to manage session state and scalability on the server and with potential cross-browser compatibility issues. Alternatively, they could write a Silverlight application in a pure .NET environment with a WPF (WinForms-like) UI that is highly functional and has clean model-view-controller separation.
…

Get the file Download here