Product Support Services should have a fix for this problem. I haven't
seen it publically released yet, but a couple of weeks ago it was supposed
to be in the final stages. Contact them, and they should be able to get
you the fix. They can contact me if they have any questions.
---
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: "Dave Wendleton" <we****@genieind.com>
Sender: "Dave Wendleton" <we****@genieind.com>
Subject: Project deployment to a Multi-Site server
Date: Tue, 5 Aug 2003 12:34:49 -0700
Lines: 11
Message-ID: <91****************************@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: AcNbiKJNLMNuvm9XSamBb1BGDwMzTA==
Newsgroups: microsoft.public.dotnet.general
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:103570
NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
X-Tomcat-NG: microsoft.public.dotnet.general
We are developing ASP.Net apps. We would like to use the
Deployment project to create MSI files that would be
installed on to the production servers. This will allow us
to have our operations department do installs at night
easily. The problem I have encountered is there seems to
be no way of targeting a specific site on the server. When
I try to install it will always go to the first site in
the list. Each site has a seperate IP and URL associated
with it; however, I can't find a way to choose a site. We
are using VS.Net 2003 and our production box is a windows
2000 server running IIS 5. Any help would be appriciated.