CSLA .NET 3.8.1 available

RockfordLhotka posted on Tuesday, November 10, 2009

I've put CSLA .NET 3.8.1 online for download. The only difference between this and 3.8.0 is that in 3.8.1 the Csla project has no dependency on ASP.NET MVC.

Let no one say that I disregard community feedback (outcry?) when I do something wrong :)

paupdb replied on Wednesday, November 11, 2009

Rocky,

Found a bug when using the 3.8.1 Csla for Silverlight release.
The assembly version number for the cslalightcs project has not been incremented - its still sitting at 3.8.0.0.
The cslacs project has been incremented though, which is causing the MobileFormatter to fail because the cslacs and cslalightcs assemblies don't match on version number.

To fix it I just updated the assembly and file version numbers of cslalightcs to match the cslacs project.

RockfordLhotka replied on Wednesday, November 11, 2009

paupdb:
Rocky,

Found a bug when using the 3.8.1 Csla for Silverlight release.
The assembly version number for the cslalightcs project has not been incremented - its still sitting at 3.8.0.0.
The cslacs project has been incremented though, which is causing the MobileFormatter to fail because the cslacs and cslalightcs assemblies don't match on version number.

To fix it I just updated the assembly and file version numbers of cslalightcs to match the cslacs project.

Thank you for finding that - I've updated the downloads to fix the issue, so if you get the *-091111.zip files all should be well.

Jimbo replied on Thursday, November 12, 2009

The assembly file version is a repeating issue, as I recall that the assembly version and file version was not maintained in many early versions of csla and sample projects etc and there is no compulsion imposed by the VS IDE to maintain this..
It is easy to forget this detail when you are committing code using the Major.Minor.Revision format as against the Microsoft Major.Minor.BUILD.revision format. and auto build versioning.or managing the assembly file in your build server.
It is the File version that matters more in the case of csla distributions. The Assembly version could be kept at (say) 3.5 until you advance to .net 4.

jimbo

RockfordLhotka replied on Thursday, November 12, 2009

This version number issue was a search-replace mistake.

I thought all the version numbers were in the 3.8.0.0 format. But it turns out that the Silverlight projects are in 3.8.0 format.

Since I don’t release binaries, I just update the version numbers in the projects. There is no automated build process, because I don’t actually do a build as such.

From: Jimbo [mailto:cslanet@lhotka.net]
Sent: Thursday, November 12, 2009 7:09 AM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] CSLA .NET 3.8.1 available

Cine replied on Thursday, November 12, 2009

Make a new file in the root of svn named AssemblyInfo.cs
which contains all the common settings, like version. And ofcourse remove the same settings from the already existing AssemblyInfo.cs files
and add this to all the relevant csproj files:

    <Compile Include="..\..\AssemblyInfo.cs">
      <Visible>false</Visible>
    </Compile>

Then you just have 1 place to update the version.