VB6 ASP IIS Application in XP

I've recently aquirred ownership of a website that was build as an IIS Application within VB6.

This website is developed and maintained within Windows NT.

I've been asked to look into the possibility of moving development of this website to a XP build machine.

There appears to be some issues in running the web classes in debug mode and I can't seem to support this website in this environment.

If I create a simple IIS Application - New Project --> IIS Application and try to run this application I get the following error (which si the same error I'm getting with my website) -


HTTP 500.100 - Internal Server Error - ASP error
Error Type:
Server object, ASP 0177 (0x800A01F3)
Invalid class string
/Project1/WebClass1.ASP, line 14


Where the asp page created is -

<%
Server.ScriptTimeout=600
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.WebClassManag er")
End If
Application.UnLock
End If

Application("~WC~WebClassManager").ProcessNoStateW ebClass "Project1.WebClass1", _
Server, _
Application, _
Session, _
Request, _
Response
%>



Does anyone out there know if there is a way of running VB6 IIS Applications in XP?

Is there a way of running a VB6 application without debugging. I'm a .NET developer and know you have 2 options when running your program in .NET - with or without debugging. Is there a similar way in VB6?

re: VB6 ASP IIS Application in XP

Got an answer to this problem which enabled me to run the Simple IIS Application I mentionned.

I think there were 2 parts to the problem.

The first consisted of ensureing the webclassmanager dll was on the XP build maching. MSWCRUN.dll was copied across and put on the machine then registered. I then ensured it was referenced correctly by the project through the Project references functionality.

This itself didn't fix my problem but I figure it did no harm.

I then managed to find a help file online (can't find the URL now though!) which mentionned this error. Their solution was to make a dll out of the project, register that dll then debug the appllication and this is what worked.

Hope this may help someone in the future.