1.Difference between ASP.NET and Silverlight
Unlike ASP.NET, the bulk of Silverlight processing occurs on the client machine thus decreasing server resource utilization and improving the Web experience on the client.
3 Asp.net is not platform independent. Silverlight is delivered as a cross-platform and cross-browser plug-in that exposes a programming framework and features that are a subset of the .NET Framework and Windows Presentation Foundation (WPF). 4 ASP.NET is a server framework for building dynamic web applications. In Asp.net most processing happens from the server side. Silverlight is a client-side framework geared at providing a rich user experience and/or other capabilities such as video streaming. In Silverlight most processing happens from the client side. 5 Both ASP.NET and ASP.NET AJAX are heavily dependent upon the ASP.NET page event life cycle, are tightly coupled to the server. Silverlight is a free plug-in that encompasses a subset of functionality from the .NET Framework and WPF.Silverlight runs in the browser as a "sandbox" - a secure zone installed into the browser that accommodates Silverlight functionality while completely protecting the host platform from any possibly adverse actions performed by Silverlight 6 Asp.net can be hosted in IIS. Silverlight can be hosted in IIS & Apache. 7 ASP.NET is Microsoft's competitor to JSP/JSF and the successor to classic ASP Silverlight is Microsoft's competitor to Adobe Flash and Flex. Basically, a standalone runtime running inside a browser allowing animation, real-time 2D and vector rendering, etc
S.No WPF Silverlight 1 WPF is mainly used for creating desktop applications. Silverlight is prominent for creating web based applications. 2 WPF extends support for advanced features of Windows OS. Few among those features are: 3D, complete documentation support and hardware acceleration. The advanced features of Windows OS namely 3D, complete documentation support and hardware acceleration are not supported in Silverlight. 3 WPF includes extensive collection of data binding properties. Silverlight does not support many data binding properties that are supported by WPF. Few properties that are not supported by Silverlight are ElementName, RelativeSource, UpdateSourceTrigger 4 In WPF, the custom markup extensions are supported through the markup extension support x:type. The x:type is not available in Silverlight. 5 In WPF, the items that are added to the control named TabControl will be wrapped automatically within the TabItem. In Silverlight, the items that are added to the control named TabControl will not be wrapped automatically within the TabItem. 6 WPF provides routed commands and all its controls are linked to commands using the property called Command. Silverlight does not provide routed commands or Command property. Silverlight provides only an interface called ICommand. The developers have to create classes that implement this interface and the custom behavior has to be defined within the class. 7 WPF offers input binding support. Silverlight does not offer input binding support.