CSLA 4 version 4.2 is now released and available for download.
The primary focus of this release is the introduction of support for mono (Mac, Linux), monotouch (iPhone, iPad), and mono for Android.
You can now reuse your business code across .NET, Silverlight, Windows Phone, and these newly supported platforms as well. As demand grows to build applications that must work on various mobile devices, the ability to directly reuse your business classes is compelling!
Version 4.2 also includes a number of enhancements to the existing CSLA 4 rule engine, along with various other features and bug fixes. Check out the change log for more information.
Very small item. The license agreement when running the installer is for version 4.0.1
Thanks for all the great work.
It is actually version 4.0.1 of the license :)
I can never understand legal mucky-de-muck anyway. 
Rocky,
I updated from the 4.2 beta to the release and something has broke. It appears to me that my ObjectFactoryLoader is not being called after I updated the csla.dll, so I rolled back to the previous beta version and it worked fine.
Todd
I have just updated a small silverlight app to use CSLA 4.2 via NuGet, and now I'm getting the following error:
Could not load file or assembly 'Csla, Version=4.2.0.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I also have downloaded the samples for Version 4.2.0 and when I run CslaSamples-4.2.0.1103\Samples\Silverlight\cs\SimpleApp I get the same error.
Can someone shed some light on it.
Thank You
Luigi
Unreal.
Silverlight ignores the last part of version numbers. So 4.2.0.1103 is 4.2.0.0 in Silverlight.
Basically this means we can't use the revision part of the version number.
That's pretty messed up, and will force me to re-release 4.2.
Rocky,
I'm using Silverlight as well. Sorry for not stating that!
Todd
I've updated the download page and nuget with 4.2.1 and I believe all is now well - grab the new version and all should be well.
I think starting with 4.3 I'm going to adopt a new versioning scheme to use the x in 4.3.x as an increment for every release. With nuget and msi setup projects the version number is important - even during the alpha/beta phases.
Just now downloaded the 4.2 installer for windows.
This is probably a stupid question but I don't understand why the 4.2 install debug BIN folder has a separate Client and Server version of CSLA.dll that are different sizes and the release bin folder only has a CSLA.dll in the Client folder.
When developing and debugging do I just take the one in the client folder and ignore that different sized one in the server folder or...?
The folder structure mirrors the structure in our dev environment - the \bin folder structure is the same.
I tried to change it, but the setup projects in VS are so fragile that it broke the setup project... I'll probably try again at some point, but I suspect it will require completely recreating the setup project from scratch, and that's time consuming and tedious (to say the least).
I'm seeing other problems with it now as well. I think you might need to pull it entirely, I think the System.Web... assemblies in the 4.2 debug server folder are still referencing CSLA 4.1 not 4.2 as I'm getting all manner of errors and there are at least two different CSLA.dll files of different sizes in there as well.
Update: just tried the nuget variation and now everything builds and runs properly. I'll use that from now on and skip the installer which is clearly broken and I would like to suggest that you pull it in order to avoid further confusion for others in future.
I'm seeing other problems with it now as well. I think you might need to pull it entirely, I think the System.Web... assemblies in the 4.2 debug server folder are still referencing CSLA 4.1 not 4.2 as I'm getting all manner of errors and there are at least two different CSLA.dll files of different sizes in there as well.
Update: just tried the nuget variation and now everything builds and runs properly. I'll use that from now on and skip the installer which is clearly broken and I would like to suggest that you pull it in order to avoid further confusion for others in future.
I can't just pull it - I need to fix it :)
This is the problem with rushing through things. I have a release process checklist, but when the 4.2.0.1103 release failed I was running through the checklist to do the 4.2.1 release quickly - in between a whole host of scheduled meetings and conference calls. I clearly missed a step in the process in the middle of all that chaos.
Now I'll need to do a 4.2.2 release to make the installer/setup work right.
Oh, you sounded down on it earlier like you were thinking of pulling it anyway. :)
I've put 4.2.2 online - both through nuget and at http://www.lhotka.net/cslanet/download.aspx
Can you do me a favor and make sure I got it all right this time?
Seems ok in that all .dll's now are 4.2.2.0, however the folders: C:\Program Files\Marimer LLC\CSLA .NET\4.2.0\Bin\Debug\Server and C:\Program Files\Marimer LLC\CSLA .NET\4.2.0\Bin\Debug\Client both have a csla.dll with different sizes as I noted before so that's unchanged or supposed to be like that (I thought there would only be one csla.dll but I might be confused on this, I just used the Client one before with 4.2.1 and it seemed fine.
I can't test the actual reference problem I had earlier without significantly changing my project structure back from using Nuget but the Nuget stuff worked fine and all tests pass after updating about 10 separate projects that go into the whole.
The NuGet link is now correct as well.
Good, thanks for the confirmation.
I have just tried to compile Csla.Ios in MonoTouch and it has 5 build errors in Csla.Core.BusinessBase. There are really 2 different errors and they are:
Line 59 Type of namespace name 'INotifyDataError' could not be found.
Line 3424 Type of namespace name 'DataErrorsChangedEventArgs' could not be found.
Note that the source code used to compile was from the downloaded msi.
What do I need to do to make it compile?
I've asked Stuart to take a look.
Unfortunately he's the only one on the dev team with a Mac. This means the rest of us can too easily make a change to the code (it is almost all shared code) that breaks iOS and we can't find out :(
I surely wish Apple didn't impose the legal requirement that iOS stuff can only compile on OS X - it makes it impossible to have things like a unified build server, or any sort of unified build at all really.
Hi jhardman,
Try getting the source code down directly from the repository. The details are on this page:
http://www.lhotka.net/cslanet/Repository.aspx
You will need MonoDevelop on Mac OSX. I am running MonoDevelop 2.8.2, Mac OSX 10.6.8, Mono 2.10.6 with Monotouch 5.0.2.
Please let me know if you still have any errors.
Regards,
Stuart Bale
Hi jhardman,
Just wanted to confirm with you that Csla.Ios is in fact 'broken' in 4.2.2.
I will co-ordinate with Rocky to arrange a fix, and let you know the outcome.
Regards,
Stuart
Thanks for the update. I had just downloaded the source code from the trunk and can also confirm that it is not compiling. I am using MonoDevelop 2.8.4.2 and MonoTouch 5.0.3 which has come out within the last week.
Cheers, Jason
Hi Stuart,
Any idea on how to get it to compile or when the fixes will be available?
Cheers.
I have managed to get it to compile. In Csla.Core.BusinessBase I had to add IOS to the #if statements where ever it mentioned __ANDROID__. I also had to add links to the new files in the Csla\Serialization\Mobile folder.
Hi Jason,
Sorry for taking a little longer to reply. For now, it might be best to grab the code at:
svn://svn.lhotka.net/csla/core/branches/V4-2-x
as this contains the latest 'release' code.
I have this morning committed a fix for the compiler directives.
I'll soon be updating the trunk with the changes you mentioned in your latest post.
I notice from this post:
http://forums.lhotka.net/forums/t/10991.aspx
that you've deployed to a device, and uncovered further issues, so I will review that over the next couple of days, and update you in that post.
Sorry you are encountering issues - you are somewhat of a pioneer in with Csla.Ios. If you'd like to email me directly, feel free to do so on stuart at stuartbale dot com.
Regards,
Stuart
Almost forgot: the NuGet link is incorrect, they probably changed the search url. It's wrong here in your post and it's wrong on the download page: http://www.lhotka.net/cslanet/download.aspx
Almost forgot: the NuGet link is incorrect, they probably changed the search url. It's wrong here in your post and it's wrong on the download page: http://www.lhotka.net/cslanet/download.aspx
They must have just changed that in the past few days - they need to adopt a permalink scheme - this isn't the first time they've done this...
Copyright (c) Marimer LLC