The Silverlight extension is deprecated and no new development will be actioned. All new features and functionality for the support of Silverlight are now handled instead by the .NET XAML extension. Please see the section of documentation entitled Existing extensions for WPF and Silverlight for more information about the .NET XAML extension and the impacts of moving to it.
Summary: This document provides basic information about the beta release of the extension providing Silverlight support for C# and VB.NET
This extension provides support for Silverlight. The calculation of Automated Function Points for your .NET analyses will be supplemented through the creation of new objects and links specific to the Silverlight framework that will link back to objects/links produced by the base .NET analyzer.
In what situation should you install this extension?
If your .NET application contains Silverlight source code and you want to view these object types and their links, then you should install this extension.
Silverlight framework support
The following Silverlight frameworks are supported by this extension:
|All versions up to 5.0|
- Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
- Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
|Quality and Sizing|
CAST AIP release
|8.3.x||C# and VB.NET|
|8.2.x||C# and VB.NET|
Supported DBMS servers
This extension is compatible with the following DBMS servers:
|Microsoft SQL Server|
|An installation of any compatible release of CAST AIP (see table above)|
Bug Fix List
Please see Silverlight 1.1 - Bug Fix List.
Download and installation instructions
Include the extension using the interface in AIP Console:
There is nothing further to do. Follow the instructions below to run a new analysis/snapshot to generate new results:
- Advanced onboarding - run and validate the initial analysis
- Advanced onboarding - snapshot generation and validation
What results can you expect?
Once the analysis/snapshot generation has completed, you can view the results in the normal manner. The following objects and links will be displayed in CAST Enlighten:
All objects are represented under the File browser > Xaml Source file folders in CAST Enlighten:
Note that if the Name Attribute of an object is present, then it will be used to display that object in CAST Enlighten. For example:
|Name not present||Name present|
The following objects are detected:
|XAML Control||call||Action Event method implemented in source file|
|XAML Control||relyOn||Set and get accessors of Property implemented in source file|
|XAML Control||relyOn||XAML Control which is used by another XAML Control|
|XAML Source File||relyOn||Referred Class|
In this section we list the most significant functional limitations that may affect the analysis of applications using Silverlight:
- Binding in code is not supported - see https://msdn.microsoft.com/en-us/library/ms742863(v=vs.110).aspx?cs-save-lang=1&cs-lang=csharp#code-snippet-1 for an example
Binding links are not handled correctly when the same binding target exists in different classes
- The direction of the data flow (Binding.Mode properties such as OneWay, TwoWay and OneWayToSource) is not supported - see https://msdn.microsoft.com/en-us/library/ms752347(v=vs.110).aspx#direction_of_data_flow for an example
- The RelativeSource property (Gets or sets the binding source by specifying its location relative to the position of the binding target) is not supported - see https://msdn.microsoft.com/en-us/library/system.windows.data.binding.relativesource(v=vs.110).aspx for an example
- Some XAML control objects which are visible in CAST Enlighten may not be seen in the CAST Application Engineering Dashboard.
- Links between XAML Control objets and code embedded in XAML are not supported.
Limitations/open bugs in Functional Release 1.1
- In Silverlight applications, the number of transactions is empty in Transaction entry points after making Silverlight XAML controls and XAML custom controls as transaction entry points, if the plugin is installed on existing triplet.