Marking Your Code Transparent

re: Marking Your Code Transparent

Scott Willeke — Sat, 01 Oct 2005 04:38:08 GMT

I think the paragraph above that begins "Method A::Bar is marked with a separate SecurityCritical attribute..." is incorrect. Instead, in the example, only the assembly and A::Foo() are decorated with the SecurityCritical attribute, which as I understand your explanation indicates A:Foo, not A::Bar, is the only critical method in the assembly example.
However, thanks for your articles on this topic they're very helpful to understanding the notion of transparent and critical code.

re: Marking Your Code Transparent

Syed Atif Shabbir — Fri, 10 Feb 2006 03:22:46 GMT

Yeah I agree with Scott. It should be A::Foo() as the SecurityCritical attriubte.

MCPD : Assemblys transparentes e opacos

Dennes — Tue, 28 Feb 2006 01:35:10 GMT

&nbsp;
O .NET 2.0 traz novos conceitos de segurança, tal como os Assemblys transparentes e opacos. Esse...

FxCop 1.35 RC1 online

FxCop — Tue, 04 Apr 2006 03:17:29 GMT

Last week we had a push to fix many of the issues reported on the forum and include them in the FxCop...

FxCop 1.35 RC1 online

FxCop — Tue, 04 Apr 2006 03:23:31 GMT

Last week we had a push to fix many of the issues reported on the forum and include them in the FxCop...

FxCop 1.35 RC1 online

Visual Studio Managed Code Analysis (FxCop) — Thu, 12 Oct 2006 19:52:19 GMT

Last week we had a push to fix many of the issues reported on the forum and include them in the FxCop

Mirror, mirror on the wall which is the securest of them all? Part Deux

codesecurely.org — Wed, 21 Feb 2007 11:04:14 GMT

The story so far … And now for more of the adventures of Jack Bauer! ;). So since I posted the first

Silverlight Security II: What Makes a Method Critical

.NET Security Blog — Fri, 11 May 2007 03:25:54 GMT

Yesterday we talked about the CoreCLR security model , and how it is built upon the transparency model