Bnaya Eshet

CLR 4.0 tip (Strong Name)

CLR 4.0 tip (Strong Name) CLR 4.0 come with some changes of the security API. one useful new API is a new way of getting evidence without   iteration loop.   and this is how it look: Code Snippet StrongName sn = typeof ( Program ).Assembly.Evidence.GetHostEvidence< StrongName >();

CLR 4.0 transparent security

CLR 4.0 transparent security CLR 4.0 come with some changes to the security model. in general the CLR 4.0 no longer assume the sandbox for the application.   you can still sandboxed your AppDomain and the CLR 4.0 will onerous that sandbox, but running the same exe from local computer or from network shared folder won't grant the exe different privileges (sandbox).   as result the security setting goes back into the administrators hands, as it was before the .NET era and application...

Changes in the CLR 4.0 security model

Changes in the CLR 4.0 security model   The CAS ( C ode A ccess S ecurity) model of the .NET is changing in CRL 4.0 . in general Microsoft has obsolete many of the CAS operations, simplify the access to security related information, and omitting the support for having security restriction at the assembly level (security restriction will solely manage by the AppDomain sandbox ).   using obsolete APIs result with warning at the compilation and exception at run-time . in general you should...