I've read Rocky's blog on setting up an n-tier Silverlight project but the assemblies seem to have changed for 4.0.0 and I'm not sure what the purpose is for the various assemblies now. I downloaded the binaries and there's are Release and Debug folders in the package. The Release folder has only Client and Server sub-folders but the Debug has a Silverlight folder as well. I'm assuming that is because Silverlight isn't fully supported in 4.0.0 yet?
The Silverlight folder contains Csla.dll and System.Windows.Interactivity.dll. I'm assuming both of these need to be referenced by the Silverlight projects?
The Client folder contains Csla.dll, Csla.Windows.dll, Csla.Xaml.dll and System.Windows.Interactivty.dll. My assumption is Csla.Windows.dll would be a needed reference for Winforms projects, Csla.Xaml.dll for WPF projects and Csla.dll and System.Windows.Interactivity.dll would be references for both?
The Server folder contains Csla.dll, Csla.Web.dll, Csla.Web.Mvc.dll and System.Windows.Interactivity.dll. These look to be the assemblies for ASP and possibly web services projects?
Which folder's version of Csla.dll should be used for the .net business object library projects?
If I've missed a relevant post somewhere I apologize. Any help you can provide would be greatly appreciated.
Dane R. Vinson
I'll be doing another preview release soon - next week some time. That should help on the SL4 side of things.
The previous prerelease was mostly focused on .NET, because SL4 was still very immature at the time - but obviously things have changed rapidly in the past couple months, and both .NET 4 and SL4 are launching the week of April 12.
CSLA 4 is the first time I've included binaries in the releases. I hope to have a setup (.msi) program to distribute at least the binaries and basic source code. I have it sort of working, so we'll see.
In any case, the projects now build to the top-level bin folder, and into debug and release folders.
That's not how it worked in the previous prerelease, but this is what's coming next week.
Copyright (c) Marimer LLC