Composite Application Guidance for WPF and Silverlight - May 2010

Welcome to the May 2010 release of the Composite Application Guidance for WPF an
d Silverlight. This file contains late-breaking information that can be useful i
n using the guidance.
============
Known Issues
============
To see the Composite Application Library known issues, see: http://www.codeplex.
com/CompositeWPF/Wiki/View.aspx?title=Known%20Issues%20%2f%20Fixes.
============
System Requirements
============
This guidance was designed to run on the Microsoft Windows 7, Windows Vista, Win
dows XP Professional, Windows Server 2003, or Windows Server 2008 operating syst
em.
WPF applications built using this guidance will require the .NET Framework 3.5 S
P1 to run and Silverlight applications will require the .NET Framework for Silve
rlight 4.
If you are using a previous version of Silverlight, please see "New in This Rele
ase" on MSDN:
http://msdn.microsoft.com/en-us/library/ff649547.aspx
Before you can use the Composite Application Library, the following must be inst
alled:
Microsoft Visual Studio 2010
Microsoft .NET Framework 3.5 SP1 (the .NET Framework 3.5 includes WPF): http://w
ww.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1A-413D-8319-81DA479
AB0D7&displaylang=en
Microsoft Silverlight 4 (this is required only if you are creating Silverlight a
pplications): http://www.microsoft.com/silverlight/
Microsoft Silverlight 4 Tools RC2 for Visual Studio 2010 (this is required only
if you are creating Silverlight applications):
http://www.microsoft.com/downloads/details.aspx?familyid=BF5AB940-C011-4BD1-AD98
-DA671E491009&displaylang=en

You may also want to install the following:

Microsoft Visual Studio 2010 SDK to compile Project Linker: http://www.microsoft
.com/downloads/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displa
ylang=en
Microsoft Silverlight Unit Test Framework to run the unit tests in Silverlight:
http://code.msdn.microsoft.com/silverlightut
White to run the acceptance tests. The acceptance tests have been developed and
verified with the White 0.1.5.0 release: http://www.codeplex.com/white
===================================
Running Acceptance Tests with White
===================================
To run the acceptance tests, you must have White assemblies in {Application dire
ctory}\Source\Lib\White folder. The acceptance tests have been developed and ver
ified with the White 0.1.5.0 release. Although other releases of White might wor
k too, it is recommended to use the aforementioned release to avoid any issues w
hen running the tests.
Steps to run the acceptance tests:
1. Download White assemblies from http://www.codeplex.com/white
(To download White 0.1.5.0 release : http://www.codeplex.com/white/Release/P
rojectReleases.aspx?ReleaseId=12756)
2. Copy the assemblies to {Application directory}\Source\Lib\White folder
3. Open and Run the acceptance test solution files.
==================================================
Compiling the Composite Application Library Source
==================================================
To compile the Composite Application Library source code, perform these steps:
1. Double-click the "Desktop & Silverlight - Open Composite Application
Library" batch file to open the solution in Visual Studio.
2. Build the solution.
- The Composite Application Library assemblies for a Desktop app
lication will be placed in the CAL\Desktop\Composite.UnityExtensions\bin\Debug f
older.
- The Composite Application Library assemblies for a Silverlight
application will be placed in the CAL\Silverlight\Composite.UnityExtensions\bin
\Debug folder.

========================================================
Solutions Included in the Composite Application Guidance
========================================================
The Composite Application Guidance includes different sample solutions. To open
them in Visual Studio, you can run the following batch files:
* "Desktop & Silverlight - Open Composite Application Library.bat"
* "Desktop & Silverlight - Open QS - Commanding QuickStart.bat"
* "Desktop & Silverlight - Open QS - Defining Modules in Code QuickStart.bat"
* "Desktop & Silverlight - Open QS - EventAggregator QuickStart.bat"

* "Desktop & Silverlight - Open QS - MultiTargeting QuickStart.bat"

* "Desktop & Silverlight - Open QS - View Discovery QuickStart.bat"

* "Desktop & Silverlight - Open QS - View Injection QuickStart.bat"

* "Desktop & Silverlight - Open RI - StockTrader Reference Implementation.bat"

* "Desktop only - Open Composite Application Library.bat"

* "Desktop only - Open QS - Commanding QuickStart.bat"

* "Desktop only - Open QS - Configuration Modularity QuickStart.bat"

* "Desktop only - Open QS - Defining Modules in Code QuickStart.bat"

* "Desktop only - Open QS - Directory Lookup Modularity QuickStart.bat"

 * "Desktop only - Open QS - EventAggregator QuickStart.bat"

* "Desktop only - Open QS - Hello World QuickStart.bat"

* "Desktop only - Open QS - View Discovery QuickStart.bat"

* "Desktop only - Open QS - View Injection QuickStart.bat"

* "Desktop only - Open RI - StockTrader Reference Implementation.bat"

* "Silverlight only - Open QS - Hello World QuickStart.bat"

* "Silverlight only - Open QS - Remote Module Loading QuickStart.bat"

====================================
Documentation
====================================
The Composite Application Guidance includes the following documentation:
* Composite Application Guidance for WPF and Silverlight - May 2010. Thi
s is the guidance documentation.
* Composite Application Library Reference October 2009. This is the clas
s library reference documentation for WPF and Silverlight. The reference documen
tation has not changed since the previous release in October 2009 targeting Silv
erlight 3.
======================================================
Composite Application Library and Code Access Security
======================================================
Composite Application Library uses all the default .NET settings with regards to
signing assemblies and code access security. It is a recommended practice to st
rong name all your assemblies, including the Composite Application Library assem
blies, shell assembly, and any modules you might want to create. This is not a r
equirement. It is possible to load assemblies that have not been signed into a (
signed or unsigned) Composite Application Library application. You can change th
is behavior by applying a .NET security policy that disallows the use of unsigne
d assemblies or one that changes the trust level of an assembly. Please note tha
t the .NET Framework does not allow you to load partially trusted assemblies, un
less you add the AllowPartiallyTrustedCallers attribute to the Composite Applica
tion Library assemblies.
For more information, check the Code Access Security section on MSDN (http://msd
n.microsoft.com/en-us/library/930b76w0.aspx).