• Q1. Is ADO.NET objects supported in Silverlight Project?

No, Silverlight project does not support normal ADO.NET objects like DataTable, DataSet, DataColumn, Database connection providers like SqlConnection, OledbConnection objects. You can use System.Data namespace but that contains Services related stuffs not ADO.NET stuffs.

• Q2. How can style elements be applied? (similar to a CSS file/skins)

Styles elements are supported in the form of application resources. An app.xaml file can be created containing an application resource Xml construct. The target type for each style is set to the control on which the style needs to be applied.

• Q3. Can you provide a list of Layout Management Panels and when you will use them?

Canvas Panel: Use a canvas for simple layouts and when there is no need to resize panel. Controls can overlapped each other when resizing the panel. Stack Panel: Use this for grouping controls in a stack (horizontal/vertical). Controls do not overlapped. Grid Panel: most flexible, multi row/columns layouts. Similar to a HTML table

• Q4. How to set Silverlight contents width as 100%?

Generally you cant set the UserControl width in % like 100% so that the Silverlight contents can spread in the full screen. To get the 100% width of the screen you can set width="auto" and height="auto".

• Q5. Which language is used to design the layout in Silverlight?

To design the layout of the Silverlight application, XAML language is used. Extensible Application Markup Language (XAML, pronounced zammel [zæm??]) is a declarative XML-based language created by Microsoft which is used as a user interface markup language to define UI elements, data binding, eventing, and other features.

• Q6. Which programming language can be used to write the backend of the Silverlight application?

We can either use Visual C# or Visual Basic to code the backend of the silverlight application. Here backend means the code behind files for the Sivlerlight pages.

• Q7. When you create a new project in Silverlight through Visual Studio, how many xaml files are created and what are the uses of those files?

When we create a Silverlight application from Visual Studio, two (2) xaml files are created into the Silverlight project. App.xaml - App.xaml is a file used to declare shared resources like brushes, various style objects etc. and to handle the global application level event (this is almost similar to global.asax file in asp.net application). By default following events are created in the App.xaml.cs file. Application_Startup Application_Exit Application_UnhandledException ReportErrorToDOM MainPage.xaml or Page.xaml - This page is the default page of the Silverlight application and when the silverlight application runs this becomes the default page to appear (this page is like the default.aspx page of asp.net application)

• Q8. How to change the default page of the Silverlight application?

To change the default page of Silverlight application, you need to set the RootVisual property inside the Application_Startup even of App.xaml file. private void Application_Startup(object sender, StartupEventArgs e) { this.RootVisual = new YourPage(); }

• Q9. How to change the default page of the Silverlight application?

To change the default page of Silverlight application, you need to set the RootVisual property inside the Application_Startup even of App.xaml file. private void Application_Startup(object sender, StartupEventArgs e) { this.RootVisual = new YourPage(); }

• Q10. What is the parent xaml tag of Silverlight page?

UserControl is the parent xaml tag of the Silverlight page. All other tags are placed under UserControl tag.

• Q11. What is the use of ClientBin folder?

ClientBin folder is used to place the .xap file of Silverlight application. You can keep this anywhere in your web application but this is the default that is used by the Silverlight.

• Q12. What is the .xap file inside ClientBin folder of consuming Silverlight application?

Following is a very good FAQ about the .xap posted on asp.net page.

• Q13. What does XAP mean?

XAP (pronounced ZAP) is the file extension for a Silverlight-based application package (.xap). This file contains the compressed assemblies and resources of a Silverlight 2 application.

• Q14. What is a .xap file?

A .xap file is a Silverlight-based application package (.xap) that is generated when the Silverlight project is built.

• Q15. Why is XAP important?

Tools, such as Visual Studio 2008 with the Microsoft Silverlight Tools Beta 2 for Visual Studio 2008, allow you to create Silverlight applications that are heavily client based using managed code. You can use managed code, such as C# or Visual Basic, and benefit by using the tools that you are used to working with.

• Q16. How does XAP work?

Once you have created the .xap file (explained below), the Silverlight 2 plug-in downloads the file and runs it in a separate work space.

• Q17. How do I use a .xap file?

A .xap file is used to contain and transfer the assemblies and resources of a managed code application. This managed code application must be run within the Silverlight 2 browser plug-in.

• Q18. What is Silverlight.js file?

Silverlight.js is a helper file which enables Web sites to create advanced Silverlight installation and instantiation experiences.

• Q19. Can we add the reference of a Class library project in Silverlight application project?

No, You cant add the reference of a Class library inside the Silverlight application project. You can only add the reference of another Silverlight application project inside a Silverlight application project. However, you can add the reference of a Web Service or WCF services.

• Q20. How to perform Event handling in silver light?.

Silverlight 1.0 uses JavaScript, while Silverlight 2.0 uses C# (managed code) for event handling. We will be describing the event model for Silverlight 2.0. The event handlers are defined in the code-behind file that backs the XAML definition of your User Interface (UI), namely mypage.xaml.cs. The Silverlight Event Mode In Silverlight, there are two event cases: Input events Non-input events. Input Events: The browser that hosts the Silverlight plug-in handles initial input stimulus for the input events. This is because Silverlight works within the plug-in architecture of the hosting browser. From the browser, the event is sent to the Silverlight plug-in. Then, it is raised as an event in the Silverlight Object Model. Non-input Events: They report a state change to a particular object, for example, the state change events that report asynchronous download state or progress of actions initiated by Web Client. Some non-input events provide lifetime information of objects at a framework level. For example the FrameworkElement.Loaded event