Disabling the FIPS Algorithm Check- March 14, 2008 .NET 2.0 introduced a check for FIPS certified algorithms if your local security policy was configured to require them. This resulted in algorithms which are not FIPS compliant (or implementations which were not FIPS certified) throwing an InvalidOperationException from their constructors. In some cases this isn't a desirable behavior. For instance, some applications need to use the MD5 hashing algorithm for compatibility with an older communication protocol or file format. ...http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx CAS and Native Code- March 4, 2008 CAS is complicated enough to understand when all of the moving parts are written in managed code (and therefore have all the associated managed meta-information like grant sets, etc). However, once native code comes into play things can get even more confusing. Let's take a look at how CAS works when there's native code on the call stack. For this discussion, lets assume we have a call stack (growing down) like so: Managed code: M1 Managed code: M2 Native code: N1 Managed code: M3.http://blogs.msdn.com/shawnfa/archive/2008/03/04/cas-and-native-code.aspx |