We’re developing a CSLA based solution which needs to run under SharePoint 2010. This unfortunately limits us to .Net 3.5 and thus CSLA 3.8.4 as the latest CSLA for .Net 3.5.
We would still like to leverage Entity Framework v4 for data access which is possible only with .Net 4.0
The workaround we’re looking at is having CSLA business library project target .Net 3.5 and WCF Portal and Data Access projects targeting .Net 4.0
I’ve made a small prototype featuring CSLA 3.8.4 client on .Net 3.5 and server/data layer on .Net 4.0. This approach seems to be working fine so far.
However I would like to hear from other CSLA members on whether this is a good practice and if there are potential issues with this approach?
My guess is that it boils down to the question of how well object serialization/deserialization works across different .Net Framework versions (3.5 and 4 on this case). Maybe Rocky can provide some clues here?
My guess is that it boils down to the question of how well object serialization/deserialization works across different .Net Framework versions (3.5 and 4 on this case). Maybe Rocky can provide some clues here?
I think that is exactly the issue, and I don't know how well this will work. The only issues I can see would arise if Microsoft changed the serializer at all for .NET 4 - but if your test is working that's encouraging. And if Microsoft changed any internal fields in core types (System.Object - not likely, ObservableCollection or BindingList - not likely, Dictionary - not likely).
There's certainly no guarantee, but it seems like it could work.
Copyright (c) Marimer LLC