Upgrading from 2.1.4.0 to 3.5.2?

RangerGuy posted on Tuesday, November 11, 2008

Hi There,

I have been building a rather large web app with C# 2.0, SQL Server 2005 and CSLA version 2.1.4.

I have not had the time to keep up with all the change logs but would like to upgrade to .net 3.5 and CSLA.net version 3.5.2. I'm wondering if anybody has done this big version jump and are there any issues I should be aware of?

Basically I guess I'm wondering if CSLA.net version 3.5.2 is backwards capatible with version 2.1.4 ?

thanks

Curelom replied on Tuesday, November 11, 2008

I've been able to migrate from 2 to 3.5.2 with only minor changes to my classes.  It isn't complely backward compatible, but pretty close.  I think looking through the change logs for breaking changes would be a good starting point.

JoeFallon1 replied on Tuesday, November 11, 2008

I plan to make this jump in a month or so.

The only issue I have really found is the spelling change for:

AddDependantProperty to AddDependentProperty

And the compiler flags them for you anyway.

The older style code should all still work.

Making the jump to Managed Properties is a whole other matter. I may only do that for new BOs that I create. Going back and fixing up all the old ones is a large task with a lot of associated risk and re-testing.

But if you ever plan to use Silverlight then you should also use Managed Properties to make things easier. You can do it without them but then you have to write code for Serialize and Deserialize for each BO.

Joe

JonnyBee replied on Tuesday, November 11, 2008

Hi,

In Csla 3.5 - Save now does a Clone of  your business objects unless you make sure ApplicationContext.AutoCloneOnUpdate is false (Config variable).

And if the EditLevel on your BO's get out of sync you will get exception when calling Save. I believe 2.1.4 was a bit more forgiving on this.

And using Linq2Sql/Linq2EF and Linq2Objects may simplify a lot of your DAL code and BO code.

 /jonnybee

RangerGuy replied on Wednesday, November 12, 2008

So it doesn't seem to be all that bad..thanks everybody that replied.... I'm excited to start learning and working with .net 3.5.

 

RockfordLhotka replied on Thursday, November 13, 2008

The other big sticking point people hit is that 3.0 made n-level undo edit level mismatches into exceptions. This helps you find UI errors (especially in Windows Forms), but it is a common type of error, and you may find yourself fixing a lot of UI issues you didn't necessarily know you had.

Of course if you have a web UI or XML service interface this is probably a non-issue.

RangerGuy replied on Thursday, November 13, 2008

Hi Rocky,

Thanks for the heads up... We have a 100% Web UI so the n-level undo is a none issue i believe.