Aaron J. Scott
|
| Posted: 06/23/2003, 8:44 AM |
|
I have had instances where the use of Option Explicit, declared in Common.asp, to cause an exception to be thrown on the Server (IIS 5, SP3). Commenting the line cures the HTTP 500 error. Why is ASP.dll having a heartache with the directive?
|
|
|
 |
Sixto
|
| Posted: 06/23/2003, 9:27 AM |
|
Option Explicit by itself should not generate any errors at all, much less an exception. most probably, the error is being triggered by the use of an undeclared variable.
To see a comprehensive error message (and not the 500 generic page), turn off the "Show Friendly HTTP Error Messages" in IE advanced options.
|
|
|
|
Aaron J. Scott
|
| Posted: 06/23/2003, 11:51 AM |
|
The issue of course being its an offending variable within the code Code Charge generated Class modules, ironically the variable had been declared within the class... Removing option explicit has had no discernable ill effects on the application.
|
|
|
|
|
