-
Type:
New Feature
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.3.0
-
Fix Version/s: 2.0
-
Labels:None
Changes to the CLR Security Model (and related changes to attributes applied to various interfaces and classes in the .NET Base Class Library) under .NET 4 mean that Spring.NET support for partial trust when compiled targeting .NET 4 'native' assemblies will require significant changes to security demands within the Spring.NET codebase.
Example articles, forum posts, etc. that begin to describe the scope of the challenges just with the (relatively) simple case of the Spring.NET-specific exceptions implementations are as follows:
http://social.msdn.microsoft.com/Forums/en/clr/thread/8261ec32-cda0-4863-92fe-4121c6d22d22
http://msdn.microsoft.com/en-us/library/system.runtime.serialization.isafeserializationdata.aspx
...though the problem with the modified security model under .NET 4 extends to well beyond just the changes to ISerializable and its impact on Spring.NET exceptions.