In many cases it is possible to take older versions of CSLA .NET and get them (with some effort) working on newer versions of the .NET framework.
I know some people were able to modify CSLA 1.5.3 to work on .NET 2.0, so it is likely that you could do the same thing to get it working on .NET 3.5.
The thing to keep in mind is that 1.5.3 is around six years old, and only takes advantage of the .NET features that existed back then. CSLA .NET has evolved rather substantially over the past six years, both to keep up with new .NET features and to answer requests from the broad CSLA .NET user community.
That's a double-edged sword for you.
Updating to CSLA .NET 3.7.1 would get you to the version of CSLA designed for .NET 3.5, and would allow you to take advantage of all the new .NET features and capabilities that have been introduced since 2004. And if you use the new features of CSLA .NET itself you should be able to radically reduce and simplify your business object code, while also gaining a lot of powerful new capabilities.
However, updating to 3.7.1 will almost certainly require major changes to your business object code. That probably goes without saying, since 3.7.1 typically requires just 40% of the lines of code you had to write in versions 3.0 and older.
So there's a very real cost to such an update - with the potential for some great benefit as a result.
But to your original question, I can say that I've never tried to get 1.5.3 to build on any current platform, but maybe someone else has tried and can provide some insight.
> If you want your app to run as-is you should have no
problem
That’s mostly true, but iirc there were some issues getting the
code from .NET 1.x to 2.0. I never did this, I just remember some forum posts
around 2005 when someone did make this shift. Again, from memory it seems like
they succeeded, but had to tweak a few things – probably around Remoting since
Remoting did change from .NET 1.x to 2.0.
Once you get to .NET 2.0 it should be smooth sailing up to 3.5,
because Jonny is absolutely correct about everything just building on the .NET
2.0 base up through 3.5 SP1.
Ahh, missed that they were already on .NET 2.0 – in which case
it should be pretty smooth sailing.
Copyright (c) Marimer LLC