Let's take a look at the architecture of silverlight1.0 (Image Source: msdn ):
In this 1.0 case, the main component is Silverlight. from the figure above, we can see that at the time of silverlight1.0, the main function of the top plug-in is to convert the XAML file, and the interaction with JS has processed download and so on, so we can use it for the core library below, the bottom multi-core rendering engine is an Optimization engine similar to an accelerator.
For details about 1.0, let's look at the architecture diagram provided by the 2.0 SDK.
OK. See the 2.0 architecture diagram provided by the SDK. A lot of things are added in 2.0 (yellow is newly added ). From the structural diagram above, we can see that the entire architecture is composed of two major components: Presentation core and browser host.
In fact, in the overall silverlight2.0 architecture, presentation core consists of two main parts:
1. Core presentation framework Library: provides some UI support, basically for user interfaces
2. It is a specific. NET Framework. Here we mainly provide some class libraries including: extended controls, data operations, network communication, CLR, DLR, etc.
Let's talk about it one by one.
First part presentation Core
1. The core Presentation Library includes all the items provided to the user interface, including inputs, UI core, DRM, media, XAML, and controls (including the layout control)
2. The rest of the. NET Framework is shown in the figure: data, DLR, CLR, WCF, and bcl. There are also some basic class libraries.
It should be noted that the data library provides the support for LINQ and LINQ to XML. How to use this feature will appear in the subsequent data binding chapter, the role of DLR (Dynamic Language Runtime) is to support multiple dynamic languages to use Silverlight, such as JScript, ironruby, and ironpython. NET developers to use Silverlight, it is estimated that flash is to be further squeezed out. BCL (base class library) is actually a programming method provided in some. Net framewrok class libraries.
The rest are some additional things mentioned in the SDK, including offline storage, asynchronous programming, file management, HTML interoperability, packaging, and XML class libraries.
From the perspective of the entire silverlisilverversion, in 1.0, it actually provides a lot of UI support, basically creating Ria, but the complexity of JavaScript operations makes mostProgramMembers are discouraged. Microsoft has added CLR in 2.0 to change the situation. net programmers pull in and add DLR, and in order to be more compatible with the WPF program to implement a one-time creation of XAML, therefore, in 2.0, we intentionally added some libraries to package the WPF stuff. In the subsequent sections. I will cover all these things.
For development tools, currently released blend 2.5 beta1 March preview version, you can create the silverlight2.0 program, but there are a lot of bugs. The official version is to release beta2 in the second quarter of this year. Other toolsArticleAs mentioned in
In addition, after the Silverlight project is compiled, it will become an xap file stored in the clientbin directory of the web program directory we tested. The test page can be displayed on the webpage by calling the xap file.
