PageRenderTime 15ms CodeModel.GetById 10ms app.highlight 2ms RepoModel.GetById 1ms app.codeStats 0ms

/V1/trunk/readme.txt

#
Plain Text | 56 lines | 43 code | 13 blank | 0 comment | 0 complexity | e001b228c53f6104ce08893ca10e27f3 MD5 | raw file
 1Composite Application Guidance for WPF - June 2008
 2Welcome to the June 2008 release of the Composite Application Guidance for WPF. This file contains late-breaking information that can be useful in using the guidance.
 3
 4============
 5Known Issues
 6============
 7To see the Composite Application Library known issues, see: http://www.codeplex.com/CompositeWPF/Wiki/View.aspx?title=Known%20Issues%20%2f%20Fixes.
 8
 9
10===================================
11Running Acceptance Tests with White
12===================================
13
14To run the acceptance tests, you must have White assemblies in {Application directory}\Source\Lib\White folder. The acceptance tests have been developed and verified with the White 0.1.5.0 release. Although other releases of White might work too, it is recommended to use the aforementioned release to avoid any issues when running the tests.
15
16Steps to run the acceptance tests:
171. Download White assemblies from http://www.codeplex.com/white 
18   (To download White 0.1.5.0 release :  http://www.codeplex.com/white/Release/ProjectReleases.aspx?ReleaseId=12756)
192. Copy the assemblies to {Application directory}\Source\Lib\White folder
203. Open and Run the acceptance test solution files.
21
22==================================================     
23Compiling the Composite Application Library Source
24==================================================
25To compile the Composite Application Library source code, perform these steps:
26
27	1. Double-click the "Open Composite Application Library Solution.bat" batch file to open the solution in Visual Studio.
28	2. Build the solution. The Composite Application Library assemblies will be placed in the CAL\Composite.UnityExtensions\bin\Debug folder.
29
30========================================================
31Solutions Included in the Composite Application Guidance
32========================================================
33The Composite Application Guidance includes different sample solutions. To open them in Visual Studio, you can run the following batch files:
34
35	* "Open Hello World Solution.bat"				             : Opens the Hello World Solution
36	* "Open QS-Commanding Quickstart Solution.bat" 			     : Opens the Commanding QuickStart Solution
37	* "Open QS-ConfigurationModularity Quickstart Solution.bat"  : Opens the Configuration Modularity QuickStart Solution
38	* "Open QS-DirectoryLookupModularity Quickstart Solution.bat": Opens the Directory Lookup Modularity QuickStart Solution
39	* "Open QS-EventAggregation Quickstart Solution.bat" 		 : Opens the EventAggregation QuickStart Solution
40	* "Open QS-UI Composition Quickstart Solution.bat" 		     : Opens the User Interface Composition QuickStart Solution
41	* "Open RI-StockTrader Reference Implementation Solution.bat": Opens the Stock Trader Reference Implementation Solution
42
43====================================
44Documentation
45====================================
46The Composite Application Guidance includes the following documentation:
47
48	* Composite Application Guidance for WPF - June 2008.chm. This is the guidance documentation.
49	* Composite Application Library Reference - June 2008.chm. This is the class library reference documentation.
50
51======================================================
52Composite Application Library and Code Access Security
53======================================================
54Composite Application Library uses all the default .NET settings with regards to signing assemblies and code access security. It is a recommended practice to strong name all your assemblies, including the Composite Application Library assemblies, shell assembly, and any modules you might want to create. This is not a requirement. It is possible to load assemblies that have not been signed into a (signed or unsigned) Composite Application Library application. You can change this behavior by applying a .NET security policy that disallows the use of unsigned assemblies or one that changes the trust level of an assembly. Please note that the .NET Framework does not allow you to load partially trusted assemblies, unless you add the AllowPartiallyTrustedCallers attribute to the Composite Application Library assemblies. 
55
56For more information, check the Code Access Security section on MSDN (http://msdn.microsoft.com/en-us/library/930b76w0.aspx).