Handled Api Regarding Silverlight Are Able To Use Compiled Languages Or Dynamic Languages

By Author: rayn law
Total Articles: 1
Comment this article

There are two kinds of Silverlight application models that Silverlight developers in UK can use to successfully conduct Silverlight development effectively. With the such application models, it's possible to generate standard, intricate and also extensible applications. These applications subsequently readily share the resources within the network. The Managed API is the 1st model that makes use of code running in the common language runtime (CLR) for Silverlight. developers incorporate the use of the managed API with compiled languages such as Visual Basic and C# or dynamic languages just like IronPython and IronRuby.

The 2nd model is that of JavaScript API for Silverlightthat use JavaScript program code interpreted by the browser. Many of the Silverlight documentation uses managed API containing more functionality to offer as compared to the JavaScript API. light-weight version of .NET framework might be accessed by applications using Managed API. Not like this, applications that make use of JavaScript API have the ability to access just ...
... the Silverlight presentation core and the browser JavaScript engine.

The Silverlight developer in UK can wrap up managed assemblies as well as source documents into application package (.xap) files with the aid of the managed API. The Silverlight plug-in helps loading of app package and pulling of the contents.

The application package needs to have an assembly that a class obtained from the app. An interaction in between the program and Silverlight plug-in occurs in Application class. With the help of the app class, the Silverlight developer in UK can present user interface in the host Web page. Life time events as well as resource management can also be presented by way of Application class.

Developers can utilize XAML markup to include user interface patterns in the managed API as well as JavaScript API. The managed API permits the developers include the application code into various XAML documents and accompanying code-behind documents. Silverlight plug-in assists loading of XAML files. With this loading, object tree is created that could be manipulated as a result of code-behind. Such rule furthermore aids manipulation of the HTML Document Object Model (DOM) by HTML Bridge.

There is only a single XAML page which gets loaded in JavaScript API as a substitute to an application package. This XAML is comprised of URI references to server-side resources for example images and also video clips. XAML can be used to generate an object tree then developers can manipulate it programmatically with the use of JavaScript in the host HTML page.

The complex apps containing inner site navigation may not be helped by the application model provided by the JavaScript API. Nevertheless, in some instances like splash screens, it is always informed to implement this application model in place of Managed API that will prove rather inconvenient. The setup of basic site navigation by Silverlight developer in UK is possible by loading new XAML pages in to the Silverlight plug-in or just by loading new Web pages in to the web browser.So as to integrate Silverlight while using the HTML Document Object Model, both the managed API and JavaScript API for silverlight can be geared to implement JavaScript in host HTML page.

Silverlight Development have to use browser-interpreted JavaScript that will interact directly with the DOM to implement almost all the developer app features. The Managed API with the use of the HTML Bridge facilitates interaction of JavaScript and DOM with Silverlight plug-in and the application model.

And as a result, these two programming models are very different given that they cannot be put into use together within a single instance of Silverlight plug-in. Nevertheless, you're able to use a splash screen that uses JavaScript API and then changes towards the managed API if the application has loaded.