CSLA .NET 2.1 is availableCSLA .NET 2.1 is available
Old forum URL: forums.lhotka.net/forums/t/1361.aspx
RockfordLhotka posted on Saturday, September 30, 2006
CSLA .NET version 2.1 is now available for download from
www.lhotka.net/cslanet/download.aspxPlease make sure to read the
Change log for this release, as there are substantial changes to validation, authorization and other parts of the framework. There are a limited number of breaking changes that may affect your code, so please review the document before attempting to upgrade from 2.0 to 2.1.
The vast majority of the changes in version 2.1 are due to the community feedback from you here on the forum. Thank you all very much for being so engaged, and for providing productive feedback and input into the process!
Brian Criswell replied on Saturday, September 30, 2006
Excellent news! Thank you for all of your work and experience that you have poured into CSLA.
RockfordLhotka replied on Tuesday, October 03, 2006
Henrik found a bug in ReadOnlyBase (
http://forums.lhotka.net/forums/thread/7103.aspx), which I've now fixed.
If you downloaded the RTM right away, you may want to re-download it with the fix. The new C#/VB archive file names are "csla20xx-2.1-RTM-061003.zip" - 061003 is the key, as the previous version had a different date.
ajj3085 replied on Tuesday, October 03, 2006
Hey Rocky,
Did a diff to see which files were updated; Web\IReportTotalRowCount.cs was missing from the latest download, but was there at some point previously. Is it supposed to be removed?
Thanks
Andy
RockfordLhotka replied on Tuesday, October 03, 2006
I moved it to Csla.Core a couple weeks ago - that interface
could be useful to more than just CslaDataSource.
Rocky
Hey Rocky,
Did a diff to see which files were updated;
Web\IReportTotalRowCount.cs was missing from the latest download, but was
there at some point previously. Is it supposed to be
removed?
Thanks
Andy
andreask replied on Tuesday, October 03, 2006
Hi
are you having problems serving the download?
I'm trying to access the link from Norway
Yours
AndreasRockfordLhotka replied on Tuesday, October 03, 2006
My ISP had an issue for a few hours this morning - it should be up now.
Rocky
> -----Original Message-----
> From: andreask [mailto:cslanet@lhotka.net]
> Sent: Tuesday, October 03, 2006 12:07 PM
> To: rocky@lhotka.net
> Subject: Re: [CSLA .NET] CSLA .NET 2.1 is available
>
> Hi
>
> are you having problems serving the download?
> I'm trying to access the link from Norway
>
> Yours
> Andreas
>
>
>
>figuerres replied on Thursday, October 05, 2006
RockfordLhotka: My ISP had an issue for a few hours this morning - it should be up now. Rocky > -----Original Message----- > From: andreask [mailto:cslanet@lhotka.net] > Sent: Tuesday, October 03, 2006 12:07 PM > To: rocky@lhotka.net > Subject: Re: [CSLA .NET] CSLA .NET 2.1 is available > > Hi > > are you having problems serving the download? > I'm trying to access the link from Norway > > Yours > Andreas > > > >
Rocky, if you ever want to have some "Mirror Sites" I think I can put the files on at least 2 different servers in FL. let me know if you want to...
Jav replied on Tuesday, October 03, 2006
This is not a bug but troublesome nonetheless.
When taking care of AddRule methods, one is bound to leave some methods that are not Shared, and where the method call is not changed to AddInstanceRule. This situation, especially in a large hierarchy, is not much fun to debug. The generated error gives no indication of the object's name, and walking through code in the debugger is no picnic either.
Is there some way to insert the name of the class in the error code message?
Jav
RockfordLhotka replied on Wednesday, October 04, 2006
That makes good sense. I have updated the code to make this
change - in cvs. It will be part of the next release (probably 2.1.1), but you
can grab the change out of cvs now if it would help you
immediately.
Rocky
This is not a bug but troublesome nonetheless.
When taking care of AddRule methods, one is bound to leave some methods
that are not Shared, and where the method call is not changed to
AddInstanceRule. This situation, especially in a large hierarchy, is not
much fun to debug. The generated error gives no indication of the
object's name, and walking through code in the debugger is no picnic
either.
Is there some way to insert the name of the class in the error code
message?
Jav
Jav replied on Wednesday, October 04, 2006
Thanks a bunch Rocky. I will download the code.
Jav
Copyright (c) Marimer LLC