Minor bug: Csla.Xaml.csproj is directing to csla.Silverlight\Resources.
<Resource Include="..\Csla.Silverlight\Resources\Error.png">
<Link>Resources\Error.png</Link>
</Resource>
<Resource Include="..\Csla.Silverlight\Resources\Information.png">
<Link>Resources\Information.png</Link>
</Resource>
<Resource Include="..\Csla.Silverlight\Resources\Warning.png">
<Link>Resources\Warning.png</Link>
</Resource>
Why is this a bug? Those files exist and the solution builds fine?
It's minor
There is just a dependency that Csla.xaml.dll requires the Csla.Silverlight project to be there.
It doesn't matter to me, but new people could be confused. The same with the output being set to ..\..\Bin\Client
I don't mind letting it be this way, i though it might had been something u forgot 
The DLL shouldn't require the project - by that time the files will have been compiled in as resources and they should be in the DLL itself.
The Csla.Xaml project requires that the rest of the CSLA solution structure be present, otherwise the solution/projects won't build. That's intentional.
And of course the output of all projects going to \Bin\Client, \Bin\Server, \Bin\Silverlight and \Bin\Wp is very intentional.
The dll doesn't require the project indeed, there is no reference.. the project requires the silverlight project to be present, that's all.
Just another difference with pre 4.0
I believe this setup is easier for developers new to csla, a good change
Before u needed several downloads to work with csla.
Copyright (c) Marimer LLC