I have an intranet application still running on CSLA 3.0.5 created with VS2005 on the .NET 2.0 platform. Still running after 2 years, deployed with ClickOnce, no problems.
I'm running the same code in VS 2010 but getting a warning "Reference CSLA does not allow partially trusted callers."
Here's what I did:
Made a copy of my original source code.
Created a clean .NET 4.0 Solution in VS2010 with no projects. (The idea is to migrate to 4.0 and SL)
Start to load all source into VS2010, but still keeping the code as ".NET 2.0".
Recompile - no problems - executing no problems.
Then why the warning? Did I miss something? Is VS2010 already that "intelligent" to warn me against these things? Should I just ignore this?
I don't know - a lot has changed in .NET from 2.0 to 4. Maybe something that used to be trusted isn't trusted anymore.
If you are going to move to SL, you can't do it with CSLA .NET 3.0 - not unless you want to reinvent all the stuff we added in 3.6 specifically to support SL.
In other words, you will be forced to at least 3.8 - but that's for .NET 3.5 and SL3 - so you should look at moving to CSLA 4 to get full .NET 4 and SL4 support.
Thanks, no worries, I'm just having fun with technology here and (boring boring - establish some level of application integration!!)
Still running without problems. Have 3 different apps and 5 web apps running on 3 different .NET platforms (2.0, 3.5, 4.0) now in one VS2010 .NET 4 solution. This is fun!
Running CSLA 3.0.5, 3.83 and 4.1 also from the same solution, also DotSpatial (GIS open-source framework - check it out)
Copyright (c) Marimer LLC