CSLA .NET

From Rockford Lhotka's Expert C# 2008 and VB 2008 Business Objects books

CSLA .NET 3.8.1 available

rated by 0 users
This post has 7 Replies | 2 Followers

Top 10 Contributor
Posts 7,309
RockfordLhotka Computer [co] Posted: Tue, Nov 10 2009 2:02 PM

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 :)

 

Rocky

Top 100 Contributor
Posts 58
paupdb replied on Tue, Nov 10 2009 10:24 PM
3.8.1 makes my life easier so yay :)
You the man Rocky


Top 100 Contributor
Posts 58
paupdb replied on Wed, Nov 11 2009 12:57 AM
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.
Top 50 Contributor
Posts 151
Luc Morin replied on Wed, Nov 11 2009 7:23 AM
RockfordLhotka:

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



Beer [B]Beer [B]Beer [B] Party!!! [<:o)]

Luc Morin, T.P.
http://www.stlm.ca

Top 10 Contributor
Posts 7,309

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.

Rocky

Top 50 Contributor
Posts 110
Jimbo replied on Thu, Nov 12 2009 6:47 AM
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
Top 500 Contributor
Posts 20
Cine replied on Thu, Nov 12 2009 8:59 AM
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.
Top 10 Contributor
Posts 7,309

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

 

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


Rocky

Page 1 of 1 (8 items) | RSS

Please contact Magenic for your .NET consulting
and CSLA .NET mentoring needs.
Please consider making a donation to help support the ongoing development of CSLA .NET.

Make donation through PayPal - it's fast, free and secure!
Why donate?
Copyright (c) 2006-2010 Marimer LLC. All rights reserved.
Email admin@lhotka.net for support.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems