Microsoft Silverlight Development

Silverlight uses XAML-based templating, not web CSS. ContentTemplate defines content presentation, ControlTemplate defines entire control structure, and Styles provide property setters. CSS is a web technology completely separate from Silverlight's XAML styling system.

Silverlight 3.0 introduced several major features including 3D Effects (for perspective transforms), Out-of-Browser Support (allowing apps to run offline), and SaveFileDialog (for user-initiated file saving). Printing was actually introduced in Silverlight 4, not Silverlight 3.0, making it the correct answer to what was NOT a new feature in version 3.0.

Silverlight 3 Tools for Visual Studio 2008 installs the Silverlight SDK, Silverlight developer runtime, and Silverlight Tools (project templates and Visual Studio integration). XAMLPad is a standalone tool that is NOT included with the Silverlight 3 Tools installation - it's a separate utility for testing XAML markup independently.

XamlPadX is a XAML editing tool. Expression Blend is a design tool for Silverlight/WPF applications. Visual Web Developer 2008 Express Edition is a free IDE that supports Silverlight development. Visual C# 2008 Expression Edition does not exist as a product - there's no C# Express Edition from Expression (Expression Studio is for designers, not programming languages).

In Silverlight XAML, the Button element requires proper attribute syntax and cannot contain arbitrary text directly as child content without proper markup. The correct syntax would be or My button content. The given code My button content is invalid and will not work.

Silverlight includes LinearGradientBrush and RadialGradientBrush (both for gradient fills) and ImageBrush (for painting with images). VideoBrush is not a standard brush type in Silverlight - video is typically displayed using MediaElement controls, not as a brush. This makes VideoBrush the odd one out.

Silverlight uses policy files to enable cross-domain network access. While crossdomain.xml is supported (for Flash compatibility), the primary and more flexible Silverlight-specific policy file is clientaccesspolicy.xml. Web.config is for ASP.NET configuration, and App.xaml is for Silverlight application settings - neither handles cross-domain policy.

This is a duplicate of question 140642. Silverlight 3 Tools for Visual Studio 2008 installs the SDK, developer runtime, and Tools. XAMLPad is NOT included in this installation - it's a separate standalone XAML testing utility.

Deep Zoom in Silverlight uses multi-resolution image pyramids (256x256 tiles) for performance, enabling fast initial load and smooth animations. Statement B claims Deep Zoom takes more time to load initially for large images, which contradicts the core purpose of Deep Zoom - it's specifically designed to load quickly by only loading necessary tiles at the current zoom level, not the entire large image.

The .xap file is a Silverlight application package generated at build time, containing AppManifest.xaml, compiled assemblies (.dll), and resources. Web pages load .xap files using object or asp:Silverlight tags. Statement B incorrectly claims .xap files are encrypted - they are actually just ZIP archives that can be opened and viewed with any ZIP utility.

Isolated storage quota CAN be increased - applications can request more space via the IncreaseQuotaAsync method, subject to user approval. The default 1MB is just the starting allocation. Options A, B, and C correctly describe isolated storage's security isolation and capabilities.

Silverlight applications run in a SANDOXED security context, NOT the same context as the hosting HTML page. This isolation is fundamental to Silverlight's security model. Options A, C, and D correctly describe sandbox boundaries, resource restrictions, and the three-tier security model.