Greetings,
I am currently using CSLA.NET v2.0.3.0. What kind of changes will be required in my BO's in order to move to the latest version? Any input greatly appreciated.
Thanks,
Kelly.
No changes should be required.
However, as I note in my blog post, you may run into some exceptions around n-level undo that will help you find any bugs you have in your current code due to mis-matched Begin/Cancel/Apply edit calls. Fixes here involve your UI code, not your business objects.
Hey Rocky - thanks for the quick reply. Was there some discussion about ValidationRules being changed that required using (calling) them in a different way?
Kelly.
Sorry, didn’t see that you were coming from 2.0.3…
Yes, there are many changes from 2.0 to 2.1, especially around
validation rules. The CSLA .NET Version 2.1 Handbook provides
documentation around the changes and how to use them.
In most cases the code changes from 2.0 to 2.1 (and thus 3.0)
are pretty straightforward: you need to change any rule methods from instance
methods to Shared/static methods, or you need to associate the instance methods
with your properties using some slightly different per-instance code
(AddInstanceBusinessRules() and AddInstanceRule()). It is best to change to
Shared/static methods though, as then you get the memory and performance
benefits of 2.1.
Rocky
From: jkellywilkerson
[mailto:cslanet@lhotka.net]
Sent: Friday, July 06, 2007 1:07 PM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] ? about moving from 2.0.3.0 to latest
Hey Rocky - thanks for the quick reply. Was there some discussion
about ValidationRules being changed that required using (calling) them in
a different way?
Kelly.
Copyright (c) Marimer LLC