As a way to undertake Silverlight development productively, Silverlight developer in UK could use 2 types of Silverlight application models. The application models support developers build simple app, intricate and extensible apps that are able to share the resources within the network The Managed API is the first model that makes use of program code running over the common language runtime (CLR) in Silverlight. The developers can implement the managed API with compiled languages such as Visual Basic and C# or even dynamic languages like the IronPython and IronRuby.
The 2nd model is JavaScript API for Silverlight. This model uses JavaScript code interpreted through the web browser. The main focus section of Silverlight documentation is monitored API which offers more characteristics when compared with JavaScript API. The light-weight version of the .NET framework could very well be used by programs utilizing Managed API. Unlike this, applications which use JavaScript API are able to access just Silverlight presentation core and the browser JavaScript engine.
It’s the managed API which lets the Silverlight developer in UK to bundle managed assemblies along with resource documents into app package (.xap) files. Application package could be loaded and contents can be taken out by the Silverlight plug-in.
The application package will need assembly that a class extracted from the program. The Application class consists of interaction between the application and the Silverlight plug-in. User interface while in the host web page can be displayed through the Application class. Additionally, it features application lifetime events plus resource management.
In both the Managed API as well as JavaScript API, Silverlight developers in UK can make use of XAML markup to add user interface designs. The managed API allows developers incorporate the application code in to various XAML files and accompanying code-behind files. When XAML files get loaded with help from Silverlight plug-in, there happens an object tree that could be manipulated by way of code-behind. Such code additionally helps manipulation of the HTML Document Object Model (DOM) via the HTML Bridge.
There is just a single XAML page which gets loaded in the JavaScript API rather than an application package. This XAML is composed of URI references to server-side resources for example images and also videos. An object tree is created by making use of this XAML that can be manipulated through JavaScript in host HTML page.
The confusing applications featuring inner navigation won’t be helped by the application model provided by the JavaScript API. Nevertheless, it assists in common situations where you can utilise managed API is too heavy as in splash screens. Silverlight developer in UK can execute simple navigation by way of loading new XAML pages in to the Silverlight plug-in or by way of loading new Web pages in to the internet browser. The developer can make use of both the managed API as well as JavaScript API for silverlight to use JavaScript in the host HTML page to combine Silverlight with the HTML Document Object Model (DOM).
So as to carry out most developer application characteristics, Silverlight Application Development is required to use browser-interpreted JavaScript that can directly interact with DOM. The Managed API with the use of the HTML Bridge aids interaction of the JavaScript and DOM with the Silverlight plug-in and the application model.
And thus, both these programming models will vary given that they can’t be chosen together with a single instance of Silverlight plug-in. Nevertheless, you could use a splash screen that uses JavaScript API and then transitions for the managed API if the app has loaded.
