UWS.RegApp.exe allows registering and unregistering web sites and applications with UltiDev Web Server Pro.

Examples:

To register local web application or site there are only three required parameters - register command, application ID, and path to folder with site files:
UWS.RegApp.exe -register appid={BFEA5241-1EAF-47C2-9E5B-ADE7AC9CE080} "/Folder:c:\ProgramData\Company\Web App"

There are lots of other parameters that can be used during application registration (see list below). For example:
UWS.RegApp.exe /r /AppID:{BFEA5241-1EAF-47C2-9E5B-ADE7AC9CE080} /Clr:2 "/VDir:/somevdir "/EndPoints:http://*:0/" "/Folder:c:\ProgramData\Company\Web App" "/AppName:My Superapp" /host:SharedNetworkService "/AppDesc:Some useful application description"

To unregister site or application one needs to provide only two arguments - unregister command and application ID:
UWS.RegApp.exe /unreg /AppID:{BFEA5241-1EAF-47C2-9E5B-ADE7AC9CE080}
UWS.RegApp.exe u /appid={BFEA5241-1EAF-47C2-9E5B-ADE7AC9CE080}

All registration/unregistration ERRORS are logged in Windows Event Log (Application).

Command line parameters are not case-sensitive, may start with '/' or '-', but it's not a requirement. Most parameter names have synonyms to simplify usage so you could just guess parameter names (see below). Parameter values are separated from parameter names by either ':' or '=' characters. Don't forget to enclose parameters with whitespaces into double qoutes, like "/dir:c:\Program Data\Whatever Else".

Boolean parameter values can be as follows: 'true' or 'false', 'yes' or 'no', 'on' or 'off', 'allow', 'deny' or 'prohibit', 'start' or 'stop'.


Parameter information:


PHYSICALDIRECTORY, type: String.
Recognized parameter name variations: path, appfolder, folder.
Description: File system or network path to the folder containing application or site files. It's a required parameter when registering an application, or launching it in interactive server.

VDIR, type: String.
Recognized parameter name variations: virtualdirectory.
Description: Vritual directory. Default value is '/'.

DEFAULTDOCUMENT, type: String.
Recognized parameter name variations: ddoc, defaultdoc.
Description: Default document to be server when request URL ends with folder name. If not specified, server will look for a document named Index or Default having an extension like Html, Aspx or other web application file extensions. If no such file is found, and directory browsing is enabled, directory document list will be returned.

REALM, type: String.
Recognized parameter name variations: domain.
Description: Realm for Basic or Digest authentication.

COMPRESSION, type: Boolean.
Recognized parameter name variations: compress.
Description: Set to true (default when registering an application) to allow response GZIP compression, provided that request is sent by a client supporting compression. Not all MIME types will be compressed, but HTML, text, XML, JavaScript, CSS and many other types will be compressed.

DIRECTORYBROWSING, type: Boolean.
Recognized parameter name variations: dirbrowsing, folderbrowsing.
Description: Set to true (default is false) to make server return list of files when requested URL ends with a folder name and folder does not contain any default documents.

BYPASSAPPSERVERFORSTATICCONTENT, type: Boolean.
Recognized parameter name variations: bypass.
Description: If set to true (default), requests for static content, like images, CSS, JavaScript, and HTML files, will be served by the web server itself, without giving application a chance to handle the request. Application files, like ASPX, SVC and AXD, are still served by the application. True value is similar to how IIS is confgured by default, and is in contrast to how old UltiDev Cassini and Visual Studio Development Web Server are set up.

IMPERSONATEWINDOWSUSERFORSTATICCONTENT, type: Boolean.
Recognized parameter name variations: impersonate.
Description: If set to true and selected user authentication schema required Windows authenticaiton, web server will use client user's access rights when serving static content files. This can be used to limit which users have access to static content files. When set to false, host process's user security context will be used to access static files to be served.

ANONYMOUSAUTHENTICATION, type: Boolean.
Recognized parameter name variations: authanonymous, anonymous, anonymousauth.
Description: If set to true (default), web server will not require Windows authentication of users in order togive them access to the application. An application can still use forms/cookie-based authentication to implement custom authorization logic to access different part of the application. When set to False, at least one other authentication schema must be chosen.

BASICAUTHENTICATION, type: Boolean.
Recognized parameter name variations: authbasic, basic, basicauth.
Description: If set to true (default value is false) and Anonymous schema is not selected, browser will require user to supply username and password. Web server does not use supplied username and password on its own and application logic would have to make final authorization decision - unless Basic Auth Against Windows setting is also set to true, in which case web server will allow access to the application if client user could be successfully authenticated against Windows.

BASICAUTHENTICATIONAGAINSTWINDOWS, type: Boolean.
Recognized parameter name variations: authbasicwindows, basicwindows, basicwindowsauth, basicauthagainstwindows.
Description: If set to true (default is false) and Basic authentication schema is selected, web server will authenticate client user against Windows before granting access to the application.

DIGESTAUTHENTICATION, type: Boolean.
Recognized parameter name variations: authdigest, digest, digestauth.
Description: If set to true (default is false) and Anonymous schema is not selected, web server will authenticate client user against Active Domain (but not local Windows user credential store). When Digest authentication is employed, browsers and other clients will send user password as a hash, not as an actual text. HTTP.SYS driver deems this situation impossible for the web server or an application to handle, and requires that user credential store could to provide access to hashed password, which AD probably does. But still, HTTP.SYS handles Digest authentication completely on its own, always against an AD, and never delegates to the web server.

WINDOWSNEGOTIATEAUTH, type: Boolean.
Recognized parameter name variations: authnegotiate, negotiate, authwinsnegotiate, authwindowsnegotiate, negotiateauth, winnegotiateauth.
Description: If set to true (default is false) and Anonymous schema is not selected, client will be required to authenticate against Windows using Kerberos. Authentication will fall back on NTLM if client does not support Kerberos.

WINDOWSNTLMAUTH, type: Boolean.
Recognized parameter name variations: authntlm, ntlm, authwinsntlm, authwindowsntlm, ntlmauth, winntlmauth.
Description: If set to true (default is false) and Anonymous schema is not selected, client will be required to authenticate against Windows using NTLM.

REGISTER, type: COMMAND, no value necessary.
Recognized parameter name variations: reg, r.
Description: A command to register an application. This parameter ignores any value specified for it.

UNREGISTER, type: COMMAND, no value necessary.
Recognized parameter name variations: unreg, u.
Description: A command to unregister an application. This parameter ignores any value specified for it.

APPLICATIONID, type: Guid.
Recognized parameter name variations: appid, appguid, aid.
Description: Application GUID. When upgrading and application, please use the same Application ID. If application with provided ID alreaady exist, it will be replaced with new settings.

LISTENENDPOINTS, type: String.
Recognized parameter name variations: listento, listenat, urls, endpoints, url, endpoint.
Description: A comma-delimited list of network endpoints that will be used by the web server to serve the application. Endpoints are in the 'address:port' format, where address is a host anme, an IP address (IPv4 or IPv6), or '*' or '+' character; and port is either 0 or a valid TCP port number. When port is set to 0, web server will find a free TCP port and assign it to the endpoint. '*' and '+' both mean "any address or host", with the difference that '+' will catch all requests to the endpoint, and '*' will allow nested applications to handle all requests not handled by the application being registered.
Be cautious with using ports 80 and 443. On Windows XP, IIS 5 (when IIS is manually installed) holds on to these ports in exclusive manner. IIS 6 and later share ports just like UltiDev Web Server does, but IIS5 and other web servers may not let your application use port 80. To mitigate this situation, consider using more than one endpoint if you use any hard-coded ports.

APPLICATIONNAME, type: String.
Recognized parameter name variations: appname, application.
Description: Optional name for the application. This name will be displayed in the Web Application Explorer.

APPLICATIONDESCRIPTION, type: String.
Recognized parameter name variations: description, desc, appdesc.
Description: Optional application description. Description is shown in the Web Application Explorer.

RELATIVEPINGPATH, type: String.
Recognized parameter name variations: pingpath, keepalivepath, keepalivepingpath, ping.
Description: Optional path to a document relative to the web site root, used by the web server to periodically call the application and ensure it's compiled and loaded into memory, thus drastically improving First Page Served time of low-traffic sites and applications, at the expense of using more memory.

INTEGRATEDWINDOWSAUTH, type: Boolean.
Recognized parameter name variations: integratedauth, integrated, windowsauth, windowsauthentication, integratedauthentication.
Description: Combines Windows Negotiate and Windows NTLM authentication settings.

ASPNETVERSION, type: Int32.
Recognized parameter name variations: clr, clrversion, aspnet.
Acceptable values: 1, 2, 3, 4
Description: Version of ASP.NET loaded used by the host process. Default value is 2 (same as 3 because values 2 and 3 can be used interchangibly as they represent same undelying version of CLR). Values 1, 2 and 3 load CLR 2 host process, and 4 uses CLR 4 host process. Setting value to 1 also causes system to ignore value of force32biton64 parameter and set force32biton64 to true.

FORCE32BITON64, type: Boolean.
Recognized parameter name variations: force32, force32bit, 32.
Description: If set to true (default is false), on 64-bit systems the application will be hosted in a 32-bit process. It's useful when the application loads native 32-bit components like MS Jet COM client. This setting is ignored on x86 systems.

APPHOST, type: String.
Recognized parameter name variations: apppool, pool, host.
Acceptable values: SharedNetworkService, SharedLocalSystem, PrivateNetworkService, PrivateLocalSystem
Description: Specifies user security context and private-or-shared type of the process hosting the applications.
Network Service user context is more restricted and is better suited for Internet-facing sites and applications. Local System user is more relaxed and makes it easier to program applications because it is close to have your web application running as Administrator. Local System, however, should not be used when hosting Internet-facing application and in other situations where hacking threats are high. Legacy UltiDev Cassini runs as Local System, while IIS in its default configuration uses Network Service or other sufficionly locked-down user accounts.
Private host process will host only the application being registered, while shared processes will host multiple other applications with the same host requirements (CLR, user context and bitness). Private hosts will ensure that stability of your application is not affected by other applications, but each instance of the host process carries a price of increased memory usage from about 10 to 40 MB per process.

SHOWERRORS, type: Boolean.
Recognized parameter name variations: showerror, errors.
Description: If set to true (default), registration application with pop up a message box if an error occurs. .

ALLOWSAVINGTOUNREGAPPS, type: Boolean.
Recognized parameter name variations: saveunregapps, savetounregapps.
Description: If set to true (default), some application settings, like endpoint addresses and ports, will be saved and reused when application is unregistered. These saved settings will be used when the application is registered again. This ensures that when a web application gets upgraded, it will occupy the same port, if during registration process it tells the system to find free TCP port. If set to false, then registration will ignore settings of saved uninstalled settings of the application with the same ID.