PRB: Do Not Modify ASP File That Is Created by the WebClass Designer

View products that this article applies to.

This article was previously published under Q191187

SYMPTOMS

Place a Response.write command just before the ProcessNoStateWebClass call in the .asp file generated by the WebClass Designer. When you navigate to that site, you see only the Response.write output. You do not see any output from your WebClass even though the code is running.

Back to the top

CAUSE

The information that the WebClass writes to the Response property is flushed by the call to Response.write in the .asp file.

Back to the top

RESOLUTION

Do not change the .asp file that is created by the WebClass designer.

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

Following is a sample .asp file created by the WebClass Designer that has been modified. Notice the Response.write "Initializing " line of code.

Back to the top

Sample Code

   <%
   Response.Buffer=True
   Response.Expires=0

   If (VarType(Application("~WC~WebClassManager")) = 0) Then
    Application.Lock
    If (VarType(Application("~WC~WebClassManager")) = 0) Then
     Set Application("~WC~WebClassManager") =
     Server.CreateObject("WebClassRuntime.WebClassManager")
    End If
    Application.UnLock
   End if

   Response.write "Initializing "

   Application("~WC~WebClassManager").ProcessNoStateWebClass "MyApp.xxx", _
     Server, _
     Application, _
     Session, _
     Request, _
     Response
   %>

When you navigate to this site, you see only the Response.write output. You do not see any output from your WebClass even though the code is running.

Back to the top