Composite Application Guidance for WPF Visual Studio Templates
As you may know, in the June 2008 release of the Composite Application Guidance for WPF we are not shipping a guidance package. So, I created two Visual Studio Templates to help you to start with the creation of a solution using the Composite Application Guidance for WPF.
![clip_image002[4]](http://blogs.southworks.net/ejadib/files/2008/07/clip-image0024.png)
You will get two kind of solution/project templates
After creating a solution using the templates, you must create in the folder where solution its located a folder named Library and copy to it the following assemblies (otherwise the solution created is not going to compile):
- Microsoft.Practices.Composite.dll
- Microsoft.Practices.Composite.Wpf.dll
- Microsoft.Practices.Composite.UnityExtensions.dll
- Microsoft.Practices.Unity.dll
- Microsoft.Practices.ObjectBuilder2.dll
Download the Composite Application Guidance for WPF templates (zip file with a VSI inside)
Any feedback is welcome. Enjoy!
Composite Application Guidance for WPF Visual Studio Templates…
As you may know, in the June 2008 release of the Composite Application Guidance for WPF we are not shipping…
The solutions do not build:
Warning 1 Could not resolve this reference. Could not locate the assembly “Microsoft.Practices.Unity”. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Shell2
Warning 2 Could not resolve this reference. Could not locate the assembly “Microsoft.Practices.ObjectBuilder2″. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Shell2
Warning 3 Could not resolve this reference. Could not locate the assembly “Microsoft.Practices.Composite”. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Shell2
Warning 4 Could not resolve this reference. Could not locate the assembly “Microsoft.Practices.Composite.UnityExtensions”. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Shell2
Warning 5 Could not resolve this reference. Could not locate the assembly “Microsoft.Practices.Composite.Wpf”. Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. Shell2
Error 6 The property ‘RegionManager.RegionName’ does not exist in XML namespace ‘http://www.codeplex.com/CompositeWPF’. Line 6 Position 19. C:\Documents and Settings\dale.barnard\My Documents\Visual Studio 2008\Projects\Shell2\Shell2\Shell.xaml 6 19 Shell2
Error 7 The attachable property ‘RegionName’ was not found in type ‘RegionManager’. C:\Documents and Settings\dale.barnard\My Documents\Visual Studio 2008\Projects\Shell2\Shell2\Shell.xaml 6 19 Shell2
Warning 8 The referenced component ‘Microsoft.Practices.Composite’ could not be found.
Warning 9 The referenced component ‘Microsoft.Practices.Composite.UnityExtensions’ could not be found.
Warning 10 The referenced component ‘Microsoft.Practices.Composite.Wpf’ could not be found.
Warning 11 The referenced component ‘Microsoft.Practices.ObjectBuilder2′ could not be found.
Warning 12 The referenced component ‘Microsoft.Practices.Unity’ could not be found.
Hi Dale, as I wrote in the post, you will need to create a folder named Library where the solution is located and copy the following assemblies to it:
Microsoft.Practices.Composite.dll
Microsoft.Practices.Composite.Wpf.dll
Microsoft.Practices.Composite.UnityExtensions.dll
Microsoft.Practices.Unity.dll
Microsoft.Practices.ObjectBuilder2.dll
Hope this helps,
Doh! Okay, I got caught not reading it closely enough. Sorry!
[...] Visual Studio Templates. The goal of these templates is to help users start with the Composite WPF project For more information about the Visual Studio Templates, see Composite Application Guidance for WPF Visual Studio Templates. [...]
Learning PRISM – Getting Started……
Now that we have covered Unity and Modularity , we can start cutting into the meat of PRISM! 2 more fundamental…