[SPRNET-1374] Support for Partial Trust under .NET 4 (native compilation) Created: 25/Sep/10  Updated: 13/Aug/12

Status: Open
Project: Spring.NET
Component/s: Spring-NET-AOP, Spring-NET-CORE, Spring-NET-DA, Spring-NET-MSG, Spring-NET-NH, Spring-NET-SCHEDULING, Spring-NET-SERVICES, Spring-NET-TESTING, Spring-NET-TX, Spring-NET-WEB, Spring-NET-WEBMVC
Affects Version/s: 1.3.0
Fix Version/s: 2.0

Type: New Feature Priority: Minor
Reporter: Steve Bohlen Assignee: Steve Bohlen
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


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:


...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.

Comment by Steve Bohlen [ 28/Sep/10 ]

More reference links:




Generated at Fri Aug 14 15:24:07 UTC 2020 using Jira 8.5.4#805004-sha1:0444eab799707f9ad7b248d69f858774aadfd250.