I've wrapped up a contract and am taking a couple of weeks off before beginning my next assignment. In the meanwhile, I'm wanting to reacquaint myself with CSLA ... something which I haven't been able to use in nearly one and one-half years.
My question is this: should I migrate from 2.0 to 2.1 and then, once comfortable with it, migrate to 3.0? Or should I go directly from 2.0 to 3.0?
I would go to 3.5 - latest released version.
Rocky keeps running into databinding bugs and fixes them as best as possible in each later version. Databinding is *much* harder to support than anyone realized at the start of this - but Rocky is pretty close now.
Be sure to get the 2 eBooks from Rocky so you can read about the changes in the framework.
Then you need to search this forum to read about managed properties - a recent breakthrough in code reduction and ease of use - but not in a book yet. You do not have to make the jump to managed properties (yet) - there is plenty more to catch up on first. But I think they are the future given that CSLA Light is going to require them. So if you plan to ever get into Silverlight you should be comfortable with them. I think the key is that Silverlight does not allow reflection and managed properties allow Rocky to write serialization and deserialization code without using reflection.
Joe
Copyright (c) Marimer LLC