How to debug component technology for ASP server
This article mainly describes how to debug ASP server-side component technology, including this complex
Error message:
One, ASP 0115 Error.
Second, the code in a separate EXE file inside the operation is good, but once into the ASP
The information that caused the call to fail
Background of this article:
In the first case: can you see this information in your browser?
Error ' ASP 0115 '
Unexpected error
/<web name>/<asp File name>.asp
A trappable error occurred in A external object. The script
Cannot continue running.
This is the ASP 0115 error that makes every programmer have a headache, this error can be caused by many reasons
The result. Many people may speculate that it might be the result of Microsoft's own bugs,
And complained that Microsoft did not give a response to the patch.
In practice there are some that are true, but in most cases this is not the case.
And a lot of it is caused by the wrong access to the Inetinfo.exe process in your own code.
The second situation: Have you ever encountered this embarrassing situation, write your own code if it is in an EXE project type
Can run well, but once you call it from an ASP page, you fail?
Again, there are many reasons for this phenomenon, and most of them are due to the fact that ASP is running
Under a particular system account, in such a context, it runs a permission that is not
Let's ignore the problem.
I think, for so long a programmer, many people have a rich and separate debugging an EXE program
Experience, but when you are writing a program running in an IIS environment, you will face the traditional
More challenges in debugging.
Although you can use VB or VC + + to write the ASP components, but the VC + + debugger will be your
The best debugging tool.
Get your components ready.
In order to debug the components you write, you have to have the information needed for debugging.
Symbols allowed in your
