Silverlight and XAML Development Quiz

Windows SharePoint Services (WSS) provides web-based collaboration sites where teams can share information and documents. Option A correctly describes WSS's core purpose - creating sites for internal information sharing and document collaboration within an organization. Options mentioning 'publicly', 'Windows applications', or 'mailing' are incorrect descriptions of WSS functionality.

RIA stands for Rich Internet Application, which refers to web applications with features and functionality similar to desktop applications.

The IZI application style guide recommends two levels of secondary windows to maintain a clean user interface and prevent excessive window nesting. More levels would complicate navigation and reduce usability.

In graphical user interface design, secondary windows can be either modal or modeless. A modeless secondary window allows the user to interact with both the primary window and the secondary window simultaneously. Thus, secondary windows are indeed modeless in certain use cases.

Hyperlinks provide versatile navigation capabilities, allowing users to jump to various destinations including secondary windows within the same application, external applications, search windows, and specific pages in navigation panes.

Silverlight controls do not natively support a DoubleClick event, unlike traditional Windows Forms controls. The Click event is available, as are states like Pressed, Normal, Valid, and InvalidFocused, but DoubleClick is not part of the Silverlight control event model.

In Silverlight and similar UI frameworks, a control can only have one direct Style applied to its Style property. While styles can inherit from other styles using BasedOn, you cannot apply multiple independent styles simultaneously to a single control.

When page content exceeds scroll length in both directions, you need scrollbars for both horizontal and vertical scrolling. The content pane (not the browser) should provide these scrollbars. Option A incorrectly refers to the browser's horizontal scrollbar, while Option D incorrectly refers to the browser's vertical scrollbar. The correct solution is to provide both scrollbars within the content pane itself.

In WPF/XAML, locally set properties always take precedence over styled properties. Even though the Style defines Background as 'Green', the direct Background='Red' setting on the Button element overrides it. This is a fundamental property value precedence rule: inline/local values > style setters > default values. The button will appear red.

In WPF/XAML, animations are incorporated using Storyboard objects. A Storyboard is a container timeline that groups and controls child animations. Options A (Motion Tween) and B (Time Line) are animation concepts from other technologies (Flash/Flex). Option D (Animation) is too generic - Storyboard is the specific XAML mechanism for defining and controlling animations in styles and templates.

RelativeSource is a MarkupExtension in WPF/XAML binding that allows you to define bindings relative to the target element, particularly useful within styles and templates. It enables binding to the element itself (Self), its parent/ancestor types, or previous data items. Options A, C, and D describe incorrect purposes. RelativeSource is specifically designed to define bindings in styles/templates where the source cannot be directly specified.

In WPF/XAML, styles can be defined at multiple levels: App.xaml (application-wide resources), inline directly on controls, and in resource dictionaries (which can be merged or defined at various levels). Option B (MainPage.xaml) is incorrect as a standalone answer - MainPage.xaml would use a resource dictionary section, but MainPage.xaml itself is not a style definition mechanism. The correct locations are resource sections, not arbitrary XAML files.

This question refers to specific brush types ('Brush.Mandatory', 'Brush.Optional', 'Brush.GlyphBackground') in an 'IZI application'. These appear to be application-specific custom brush definitions. Options A, B, and C represent three distinct brush categories in this specific application's styling system. Option D ('Brush.Foreground') and Option E ('Brush.RedStroke') are not part of the defined brush types in this IZI application styling system.

In WPF/XAML, when Margin is specified with two numbers like Margin='5,5', the syntax is 'Left, Top' and the Right and Bottom default to the same values. So Margin='5,5' means Left=5, Top=5, Right=5, Bottom=5. This is shorthand for uniform margin on all sides. Option C correctly identifies this uniform application. Options A and B incorrectly assume some margins would be zero.

Expression Blend 3 is a Microsoft design tool for WPF and Silverlight applications, not for Flash. Flash is an Adobe technology platform. Expression Blend was designed specifically for creating XAML-based interfaces for Microsoft technologies (WPF, Silverlight, Windows Phone). It does not support Flash development or Flash UI components.

The IZI application is optimized for a screen resolution of 1280x1024 pixels. This resolution provides adequate screen real estate for displaying all UI elements and controls clearly while maintaining compatibility with standard monitors. Lower resolutions like 800x600 or 1024x768 may cause layout issues or require scrolling to access all features.