CSLA 4: 3 Different Csla.dll for regular .NET vs WPF vs Silverlight

Lord02 posted on Friday, April 01, 2011

Hi,

I downloaded the example for CSLA 4.0.1 ... ( from: http://www.lhotka.net/files/csla40/CslaSamples-4.1.0-110118.zip )

Are there now 3 different CSLA.DLL to include in our projects ? One for .NET, one for WPF and one for Silverlight ? Total of 3 ... ?

There are 3 subfolders in the Dependencies folder ...
namely the "Net", "Sl" and "Wp" folders.

The csla.dll in WPF folder is 286KB

The csla.dll in Sliverlight folder is 300KB

The csla in .NET folder is 371KB

What is the difference between these DLL's ?

Kind regards,

 

Lord02 replied on Friday, April 01, 2011

I noticed in the details description for each CSLA.DLL they say in the description field:

.NET folder:
"CSLA.NET for Windows (server)"

Sl folder:
"CSLA.NET for Silverlight"

Wp folder:
CSLA.NET for Windows Phone

Please explain ... which DLL would I use for:
*Regular Windows Forms
*WPF
*Silverlight
*ASP.NET Webforms

Kind regars,

RockfordLhotka replied on Friday, April 01, 2011

This is explained in Table 18 in the Using CSLA 4: CSLA .NET Overview ebook.

A summary of the sub-folders in the \bin folder:

• Client - assemblies built for the .NET 4 Client Profile
• Server - assemblies built for the .NET 4 Full Profile (with the exception of Csla.dll, which is the same as in the Client folder)
• Silverlight - assemblies built for Silverlight 4
• Wp - assemblies built for WP7

Technologies like WPF and Windows Forms typically run in the Client Profile. Technologies like ASP.NET and WCF run in the Full Profile. But those are defaults, and you can change them in your projects.

Silverlight is Silverlight.

WP7 is WP7.