http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx.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 InvalidOperationExceptionen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx#9562571Wed, 22 Apr 2009 19:00:15 GMT91d46819-8472-40ad-a661-2c78acb4018c:9562571Eric<p>WOW... this setting has SAVED us. &nbsp;</p> <p>Even asp.net 3.5 uses Page.EncryptString in several places, which creates a Rj algorithm even though it won't be used. &nbsp;Without this switch, we couldn't even use a lot of asp.net.</p>http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx#9627189Tue, 19 May 2009 10:32:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:9627189Ronak jain <p>What is the Full form of FIPS .</p>http://blogs.msdn.com/shawnfa/archive/2008/03/14/disabling-the-fips-algorithm-check.aspx#9634321Fri, 22 May 2009 00:09:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:9634321shawnfa<p>Federal Information Processing Standard</p> <p>-Shawn</p>