This topic contains the following sections.
- Programming Model Considerations
- Related Topics
Programming Model Considerations
A splash screen is an initial content area that is displayed to the user while other content is still loading. In terms of design and purpose, a splash screen has relatively low UI and interactivity requirements. The main purposes of a splash screen are the following:
Present an interesting visual.
Provide feedback to the user that the application (or browser host) is still functioning as expected and that the download is progressing.
Give specific information on download progress.
Silverlight 1.0–Era Content and Maintenance
The Silverlight 2 plug-in supports a compatibility mode that supports applications written in the Silverlight 1.0 time frame. In particular, the plug-in can initialize based on the Silverlight 1.0–era string for application passed to the object element, and/or a version of "1.0" passed to Silverlight.js for initialization. Sites that were originally written for Silverlight 1.0 should generally continue to function for clients that have the Silverlight 2 plug-in.
Developer Level of Experience
The majority of the documentation for Silverlight 5 covers the managed API. For instance, if you want to learn more about animation, you might go to Animation Overview, which contains XAML examples that are mostly the same for both APIs. But the topic also contains managed code examples and addresses some managed code-specific scenarios. You should still be able to learn the concepts independent of what languages the code examples are in.
XAML is case sensitive, because it follows XML rules. The XAML syntax and equivalent scripting are usually presented on a single page, so there was a need to standardize on the XAML-enforced casing. The titling you see in Silverlight documentation is in the correct case form for a XAML object element or attribute.