When you're using a delay-signed strongly-named assembly in ASP.NET you might get this error:
Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: The check of the signature failed for assembly 'MyAssembly'.Source Error: Line 229: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />Line 230: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />Line 231: <add assembly="*" />Line 232: </assemblies>Line 233: </compilation> Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 231
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: The check of the signature failed for assembly 'MyAssembly'.Source Error: Line 229: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />Line 230: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />Line 231: <add assembly="*" />Line 232: </assemblies>Line 233: </compilation>
Source File: c:\windows\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 231
Even if you've set up verification skipping with sn.exe -Vr, you'll need to restart the ASP.NET worker process before it takes effect as the information is only read when the process is first started.
Scott at DevReach in Bulgaria in October
Developer Stand up Comedy - Coding 4 Fun
TechDays/DevDays Netherlands and Belgium:
Posts by Category Posts by Month
Greatest Hits Dev Tools List