Hi
I know that it was not possible to run VB6 IIS Application from the IDE on Windows 7 64-bit. Does anyone know if this has changed with Windows 8?
If it has then I will upgrade the OS immediately!
best regards
Peter
Printable View
Hi
I know that it was not possible to run VB6 IIS Application from the IDE on Windows 7 64-bit. Does anyone know if this has changed with Windows 8?
If it has then I will upgrade the OS immediately!
best regards
Peter
Are you sure you "know" this?
No, nothing would have changed.
thanks for the reply.
yes, I am absolutely sure.
I suspect that Session 0 Service Isolation is the largest factor at play here. That did not go away in Windows 8, which is actually Vista R3 (i.e. Windows NT 6.2).
I can debug my VB6-COM-dlls from the context of an (classic-ASP-enabled) IIS, all running on Win7-64 - and I don't think, that the behaviour will be different in Win8...
Well - it's not exactly your scenario, because I don't use the VB6-IIS-Designer-Templates to debug "WebClasses" - but the "plain VB6-ActiveX-Dll-projects" are not *that* far off...
Meaning, when you use the normal Dll-Project-Play-Button-stuff, which allows OutOfProcess-marshalled Method-call debugging with any VB6-AX-Dll-Project...
Here's a Screenshot:
http://vbRichClient.com/Downloads/AspDebugging.png
I'm not exactly sure what I did in which order (was about one year ago, when I set this up) - but looking at it again:
- it seems I've forced it, to run the Application-Pool-(ServiceProcess) under my normal User-account (the same one, I use to log into my system)
- and then of course the "Activate 32Bit Apps" was set to True"
http://vbRichClient.com/Downloads/AppPoolConfig.png
For a bit more comfort in the VB-Dll-Project (when I'm about to enter the Debug-Mode by pressing the Play-Button) -
I've put the IISReset.exe as the "to-be-shelled-on-startup"-entry into the Debug-Tab:
http://vbRichClient.com/Downloads/IISReset.png
Here's the test-script-content of the small, serverside iisdebug.asp, which I was addressing in the Browser-URL in the Screenshot at the Top of this posting...
(it's just a simple re-delegation --- in a principally similar way, as the VB-WebClasses generate those redirect-handler-scripts too).
And here's the VB-Code for the small cTest-Class - which is seen in the Top-Screenshot too.Code:<%
Response.Write "Just an entry-line, to show that we are ""in-the-asp-script"" (about to call the COM-lib)<br></br>"
Server.CreateObject("AspCom.cTest").DoItWith Server, Request, Response, Session
Response.Write "<br></br>Ok, that apparently went well... since this line is usually not reached, when the COM-call wasn't successful"
%>
Not sure, if you want to experiment with that, to see if you can make it work with the VB6-WebClass-ProjectType too,Code:Option Explicit
Public Sub DoItWith(Server As Server, Request As Request, Response As Response, Session As Session)
Response.Write "The WebApps Root-Path is: " & Server.MapPath("/") & "<br>"
Response.Write "The Scripts Path-Info is: " & Request.ServerVariables("PATH_INFO") & "<br>"
Response.Write "The ServerTime is: " & Now
End Sub
since I can imagine, that a small VB6 and IIS containing XP-VM would not be all that far off as an alternative...
Olaf
Hi Olaf
thanks very much for the reply. I walked through the steps and I am able to debug the code.
Unfortunately since VB6 IIS applications rely so much on web classes and designer templates (with tag-replacement and all) it is not the same.
I think I will have to go for a Hyper-V XP VM instead.
thanks
//Peter