NotSupportedException: This method uses CAS policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the legacyCasPolicy configuration switch. Please see http:\/\/go2.microsoft.com\/fwlink\/?LinkId=131738 for more information.<\/P>\n
What does this mean? In earlier versions of the .NET Framework, Code Access Security (CAS) Policy was the primary mechanism for defining whether or not certain classes of managed applications were able to perform security sensitive operations or not. While powerful, CAS Policy was extremely difficult to use and manage \u2013 developers and administrators would have to set up and analyze complicated policy trees to determine what their code would be granted. Furthermore, these restrictions could be circumvented by simply using unmanaged code!<\/P>\n
We\u2019ve provided cleaner, more appropriate mechanisms for managed code security in .NET Framework 4; those will be described in detail in future posts. CAS Policy has been rendered obsolete as a result of this, hence the exception messages. It is, however, still there for those migrating apps and projects that still require CAS policy in the meantime. <\/P>\n
Note that by enabling CAS for your project, you\u2019re subjecting yourself to the CAS security policy decisions of the runtime. If you made any changes (via caspol.exe, etc) to CAS policy in previous versions of the runtime, these will not be reflected in .NET Framework 4 even with CAS policy turned on<\/I>. Your custom policy will have to be reconfigured with the .NET Framework 4 caspol.exe.<\/P>\n
If you\u2019re using CAS policy implicitly<\/A> (for example, an Assembly.Load with Evidence) or explicitly<\/A> (SecurityManager.PolicyHiearchy), check out Shawn Farkas\u2019 blog<\/A> for guidance on the new, supported mechanisms for sandboxing and running partial trust code.<\/P>\n Follow these steps to enable CAS Policy for your project:<\/P>\n 1. Go to \u201cProject\u201d in the menu bar, then \u201cAdd New Item\u2026\u201d<\/P>\n 2. Select \u201cApplication Configuration File\u201d from the list of items available.<\/P>\n 3. Enable CAS Policy via the following switch:<\/P>\n <configuration><\/P>\n <runtime><\/P>\n <legacyCasPolicy enabled=”true” \/><\/P>\n <\/runtime><\/P>\n <\/configuration><\/P>\n 4. CAS Policy is now enabled and enforced for this project. <\/P>\n If you\u2019re simply trying to get loads from remote sources (i.e. Assembly.LoadFrom(@”http:\/\/…”)) to work, you don\u2019t need to enable CAS Policy to do this \u2013 replace legacyCasPolicy<\/B> with loadFromRemoteSources<\/B> in the example above and you\u2019ll be able to load from any location. Please do note that these assemblies will be loaded as fully trusted<\/U>! You can find more information on this switch here<\/A>.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":" If you\u2019re migrating a VS project over to VS 2010 Beta1 and you are calling code that is passing Evidence objects to the runtime expecting security policy resolution, or if you\u2019re using a permission Deny, you may run into the following exception: NotSupportedException: This method uses CAS policy, which has been obsoleted by the .NET […]<\/p>\n","protected":false},"author":342,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685],"tags":[],"class_list":["post-1653","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet"],"acf":[],"blog_post_summary":" If you\u2019re migrating a VS project over to VS 2010 Beta1 and you are calling code that is passing Evidence objects to the runtime expecting security policy resolution, or if you\u2019re using a permission Deny, you may run into the following exception: NotSupportedException: This method uses CAS policy, which has been obsoleted by the .NET […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/1653","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/342"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=1653"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/1653\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=1653"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=1653"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=1653"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"clip_image002\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/10\/2019\/02\/clip_image002_thumb.jpg\" "\\"clip_image002\\"")
<\/A><\/P>\n![\"clip_image004\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/10\/2019\/02\/clip_image004_thumb.jpg\" "\\"clip_image004\\"")
<\/A><\/P>\n![\"clip_image006\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/10\/2019\/02\/clip_image006_thumb.jpg\" "\\"clip_image006\\"")
<\/A><\/P>\n