In the ServerConfig program, there's a comment that says "The base script is driven by the ServerConfig section in Thybrids.ini and you can customize operation there." In the INI file, there's information on the virtual folder (at least if you run a virtual locally while developing). But the ServerConfig also has a virtual folder name section and says if you don't want to configure a virtual, you can just leave that blank. These things seem to conflict. Is the ServerConfig controlling this with its virtual (or not) setting or is it the INI that's determining if a virtual is created. This may be "complexified" by my use of a virtual in local development, but a root-level (full-fledged) site on the production server.
The setup settings are only used for when you run the configuration. Yeah if you have multiple setups you'll have to switch, but it's unlikely you'd run this on a dev machine (unless you move the app to a new folder and point IIS at that). Basically you set that value for you want to use on your production server (ie. blank or /).
+++ Rick ---
Ok, when you say "setup settings" you mean what's used when I run my EXE and pass the CONFIG parameter, right? But given the comment about "The base script is driven by the ServerConfig section in Thybrids.ini" it still seems like there are two places where the virtual is set (or not) and so I wonder what happens when they conflict. I guess, for now, I should change the INI on the server so that there is no virtual entry (not sure if I should remove it or "blank it out"), then run the EXE in config mode and also pass the name of the root level site.
Also, that config section in the INI file has this:
[ServerConfig]
IISPath=IIS://localhost/w3svc/6/root
with that IISPath set there, is passing it when running the program (MyApp.EXE config "IIS://localhost/w3svc/6/root") really necessary. (I've changed it to 6, since that's what I'll need.)
The Web Site Id will be different on every machine. So yes you'll want to configure it specifically for each machine or pass it in to the yourApp.exe CONFIG "<IISPath>" as a parameter.
+++ Rick ---