Hi everyone.
I'm currently using CSLA 2.0 in a VB.NET 2005 application. I've read about all the good fixes etc going to version 2.1 and was planning on implementing that.
Is 2.1.4 a good stable version if I plan using VS2005 for awhile, or should I go ahead and make the leap to one of the 3.x versions?
I'm fairly new to this stuff so I'm trying to take small steps and not get confused/overwhelmed.
Any quick advice?
I have been using 2.1.4 with VS 2005 for about a year now. It is fine for ASP.Net.
I understand the 3.x versions have some major Winforms databinding fixes. So if you need that then you should make the jump.
Read the eBooks before moving ahead and peruse some of the older threads in this forum too.
I have plans to jump to 3.5 later this year when it is out of Beta.
The code changes from 1.x to 2.x were huge. It took my entire team almost a month to fix up all the BOs and pages. A quick look at 3.x shows that the required changes are minimal and things should "just work". I need to do more in depth study though. If we later want to use some of the new features (like all the Property code reduction Rocky worked so hard on) then we can optionally switch over for new BOs. And later go back and re-generate older BOs. But I don't envision major changes right away as we have tons of work ahead of us.
Joe
Thanks for the reply Joe. I'm using CSLA in a WinForms application right now. I'll have to do some reading. I don't want to bite off more than I can chew.
Thanks as always for the quick reply.
Then you should plan on moving to 3.5.
You can begin while the code is in Beta as it is fairly solid. But you have to expect to update the CSLA.dll when the final release occurs.
You do not have to use the new features - you can work into them later if you want to.
I think the original Property code is simpler to understand and code. But I have not worked with the new stuff yet. I realize it has some additional potential that can be exploited if necessary. It can be learned over time.
Joe
JoeFallon1:
Then you should plan on moving to 3.5.
Copyright (c) Marimer LLC