http://blogs.msdn.com/erwinvandervalk/archive/2009/01/30/prism-v2-drop-10-composite-application-guidance.aspxToday, we have released what’s likely going to be the last drop of Prism before the final release. You can get the release from: http://www.codeplex.com/CompositeWPF/Release/ProjectReleases.aspx?ReleaseId=22566 During this iteration, we have mostly workeden-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/erwinvandervalk/archive/2009/01/30/prism-v2-drop-10-composite-application-guidance.aspx#9385860Sat, 31 Jan 2009 08:58:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:9385860 prism v2 ??? drop 10 (composite application guidance) &raquo; Click &amp; Solve <p>PingBack from <a rel="nofollow" target="_new" href="http://www.clickandsolve.com/?p=2423">http://www.clickandsolve.com/?p=2423</a></p> http://blogs.msdn.com/erwinvandervalk/archive/2009/01/30/prism-v2-drop-10-composite-application-guidance.aspx#9458580Wed, 04 Mar 2009 18:17:34 GMT91d46819-8472-40ad-a661-2c78acb4018c:9458580alt_fo<p>I recently downloaded the v2 from MSDN. I donr see desktop in the Assembly name. How do i use it in WPF? Both the Silverlight and WPF Assembly will look the same then.</p> http://blogs.msdn.com/erwinvandervalk/archive/2009/01/30/prism-v2-drop-10-composite-application-guidance.aspx#9458639Wed, 04 Mar 2009 19:14:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:9458639erwinvandervalk<p>The only reason we had the .Desktop and .Silverlight extension in the assembly name, was to prevent a filename collision in Team Build. </p> <p>After changing the build to 'in place' build, the .Desktop extension was no longer needed. </p> <p>If you look in the directory structure, you'll find Silverlight and Desktop folders. If you are only interested in building WPF app, you should get the dll's from the desktop folders. </p>