By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,122 Members | 1,559 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,122 IT Pros & Developers. It's quick & easy.

Deploying on non-standard port w/multiple virtual directories

P: n/a
In our setup project, we have the standard web
application folder, but we also have 4 web custom folders
(virtual directories) that are created at the same level
as the web application folder (i.e. not subdirectories).
The setup works fine as long as the user leaves the
default setting of port 80. If they choose something
different, the install program loads the web application
folder correctly at the non-standard port, but it
installs the other 4 virtual directories (web custom
folders) in the standard port 80 web. I realize I can
hardcode a port number in the properties for each web
custom folder, but then the install program becomes
specific to each customer. Does anyone know of a way to
tell a web custom folder to use the same port that was
selected by the end-user during the install process for
the main web application folder?

-Greg W.
Nov 17 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
So, there is a way to do this... You need to know the Property property
values for each of your Web Custom Folders. Typically, they are something
like NEWWEBPROPERTY1.

Then, you need to run your install from the command line. Let's say your
web server is on port 20 instead. You also need to include TARGETPORT for
the Web Application Folder. So, your command line would look like this for
just one web folder, add more PROPERTY=VALUE pairs for each web folder...

msiexec /i mywebsetup.msi TARGETPORT=20 NEWWEBPROPERTY1PORT=20

That should redirect each listed folder's port to the specified port.

You might want to remove the Installation Address dialog, since if someone
changes the port in the UI during install time, the Custom Web Folders will
use the command line value.
---
David Guyer - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Content-Class: urn:content-classes:message
From: "Greg W." <an*******@discussions.microsoft.com>
Sender: "Greg W." <an*******@discussions.microsoft.com>
Subject: Deploying on non-standard port w/multiple virtual directories
Date: Thu, 13 Nov 2003 11:39:46 -0800
Lines: 18
Message-ID: <03****************************@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcOqHeTFIi70zHrCSt+2NoOrTsBwvg==
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:190742
NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

In our setup project, we have the standard web
application folder, but we also have 4 web custom folders
(virtual directories) that are created at the same level
as the web application folder (i.e. not subdirectories).
The setup works fine as long as the user leaves the
default setting of port 80. If they choose something
different, the install program loads the web application
folder correctly at the non-standard port, but it
installs the other 4 virtual directories (web custom
folders) in the standard port 80 web. I realize I can
hardcode a port number in the properties for each web
custom folder, but then the install program becomes
specific to each customer. Does anyone know of a way to
tell a web custom folder to use the same port that was
selected by the end-user during the install process for
the main web application folder?

-Greg W.


Nov 17 '05 #2

P: n/a
That's great. Thanks for the info David.

-Greg
-----Original Message-----
So, there is a way to do this... You need to know the Property propertyvalues for each of your Web Custom Folders. Typically, they are somethinglike NEWWEBPROPERTY1.

Then, you need to run your install from the command line. Let's say yourweb server is on port 20 instead. You also need to include TARGETPORT forthe Web Application Folder. So, your command line would look like this forjust one web folder, add more PROPERTY=VALUE pairs for each web folder...
msiexec /i mywebsetup.msi TARGETPORT=20 NEWWEBPROPERTY1PORT=20
That should redirect each listed folder's port to the specified port.
You might want to remove the Installation Address dialog, since if someonechanges the port in the UI during install time, the Custom Web Folders willuse the command line value.
---
David Guyer - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.--------------------
Content-Class: urn:content-classes:message
From: "Greg W." <an*******@discussions.microsoft.com>
Sender: "Greg W." <an*******@discussions.microsoft.com>
Subject: Deploying on non-standard port w/multiple virtual directoriesDate: Thu, 13 Nov 2003 11:39:46 -0800
Lines: 18
Message-ID: <03****************************@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcOqHeTFIi70zHrCSt+2NoOrTsBwvg==
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:190742NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

In our setup project, we have the standard web
application folder, but we also have 4 web custom folders(virtual directories) that are created at the same levelas the web application folder (i.e. not subdirectories).The setup works fine as long as the user leaves the
default setting of port 80. If they choose something
different, the install program loads the web applicationfolder correctly at the non-standard port, but it
installs the other 4 virtual directories (web custom
folders) in the standard port 80 web. I realize I can
hardcode a port number in the properties for each web
custom folder, but then the install program becomes
specific to each customer. Does anyone know of a way totell a web custom folder to use the same port that was
selected by the end-user during the install process for
the main web application folder?

-Greg W.


.

Nov 17 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.