Deploy Asp.Net site when multiple sites exist on server

[Marcus]

I have seen many posts of people with the same problem as me (attached
below), but I have yet to see any solutions posted. Has anyone figured
out how to deploy an Asp.net web site to the webserver in any place
other than the default website? I do not want to install it there as
our IIS has multiple websites, but nowhere is there an option when
creating the install package in Visual Studio to specify what website
on the server you want to install to. I am using VS 2002.

Anyone?

Thanks,
Marcus
From: Steve (sd*****@skura.com)
Subject: Re: Deployment to NON-default website?
View: Complete Thread (5 articles)
Original Format
Newsgroups: microsoft.public.dotnet.framework.aspnet
Date: 2002-10-22 07:54:39 PST
With regards to my original post, Microsoft has confirmed
this to be a bug. Let's hope they get this fixed in the
next service release.

-----Original Message-----
Steve,

I think you are talking about the deployment packages created by VisualStudio.Net. No "deployment packages" are created by ".Net". It is true thatcurrently the prefab ASP.Net installer created by VS.Net will only deploy tothe default website, but there is nothing stopping you from from creatingyour own installer that will create a new website in IIS and setting up yourapplication there. You might want to check into the ADSI groups for info onhow to do this. Sample scripts and documentation are provided with IIS.
-- PBR

"Steve" <sd*****@skura.com> wrote in message
news:733801c276d6$866dfff0$35ef2ecf@TKMSFTNGXA11. ..

Actually the deployment packages created by .NET will only
install under the Default Web Site as stated by Microsoft.
If you have multiple web sites on the same server (which
is very common), this install package will only install
under the Default Web Site. Yes, you can change the
default web site in IIS but this doesn't work as far
as .NET is concerned.

As I type this I am in communication with 4 different
developers with Microsoft to try and resolve this issue.
I gave in and am using one of are support tickets. As far
as I'm concerned this is a bug and I will not be charged
for the support.

Apparently, many have this problem.
So, when I get the solution, I will take the time to
spread the word.
Until then...

>-----Original Message-----
>I'm not sure I understand the problem. You can deploy ASP.NET applications >to any instance of web sites on IIS and they will run fine, unless of course >you've hardcoded something that relies on the default web site
>
>-- PBR.
>
>"Steve" <sd*****@skura.com> wrote in message
>news:00c701c27649$df0a7590$9de62ecf@tkmsftngxs01. ..
>> How? Please someone must have the answer.
>> It is not uncommon for shops to have web servers with
>> multiple web sites on them. Multiple websites with
>> individual IP's, same port...
>>
>> Microsoft are you listening?
>> This is extremely important becasue a Partner this will be
>> the stopper for us to pursue anymore .NET devlopment.
>> Simply copying files won't when you're developing complex
>> web applications.
>>
>> A urgent reply is necessary.
>> Replys may go here and/or to the above email address.
>> Thanks.
>>
>
>
>.

[Elizabeth Newman [MS]]

Marcus,

A patch has been created for Visual Studio 2003 to fix this problem. Please call PSS and ask for the "Web Setup patch." If you have any problems, please feel free to give my name to the
support technition.

Hope this helps,
Elizabeth Newman

--------------------

From: ho**********@hotmail.com (Marcus)
Newsgroups: microsoft.public.dotnet.framework.aspnet,microsoft .public.vsnet.setup
Subject: Deploy Asp.Net site when multiple sites exist on server
Date: 16 Feb 2004 17:43:44 -0800
Organization: http://groups.google.com
Lines: 97
Message-ID: <17**************************@posting.google.com >
NNTP-Posting-Host: 199.212.20.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1076982224 5074 127.0.0.1 (17 Feb 2004 01:43:44 GMT)
X-Complaints-To: gr**********@google.com
NNTP-Posting-Date: Tue, 17 Feb 2004 01:43:44 +0000 (UTC)
Path: cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTN GP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!newsfeed.icl.net!ne wsfeed.fjserv.net!nx02.iad01.newshosting.com! newshosting.com!elnk-atl-nf1!newsfeed.earthlink.net!border2.nntp.ash.gigane ws.com!border1.nntp.ash.giganews.com!nntp.giganews .com!news.maxwell.syr.edu!postnews1.google.com!not-
for-mailXref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.setup:4678 microsoft.public.dotnet.framework.aspnet:210664
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

I have seen many posts of people with the same problem as me (attached
below), but I have yet to see any solutions posted. Has anyone figured
out how to deploy an Asp.net web site to the webserver in any place
other than the default website? I do not want to install it there as
our IIS has multiple websites, but nowhere is there an option when
creating the install package in Visual Studio to specify what website
on the server you want to install to. I am using VS 2002.

Anyone?

Thanks,
Marcus
From: Steve (sd*****@skura.com)
Subject: Re: Deployment to NON-default website?
View: Complete Thread (5 articles)
Original Format
Newsgroups: microsoft.public.dotnet.framework.aspnet
Date: 2002-10-22 07:54:39 PST
With regards to my original post, Microsoft has confirmed
this to be a bug. Let's hope they get this fixed in the
next service release.

-----Original Message-----
Steve,

I think you are talking about the deployment packages created by

Visual

Studio.Net. No "deployment packages" are created by ".Net". It is

true that

currently the prefab ASP.Net installer created by VS.Net will only

deploy to

the default website, but there is nothing stopping you from from

creating

your own installer that will create a new website in IIS and setting

up your

application there. You might want to check into the ADSI groups for

info on

how to do this. Sample scripts and documentation are provided with

IIS.

-- PBR

"Steve" <sd*****@skura.com> wrote in message
news:733801c276d6$866dfff0$35ef2ecf@TKMSFTNGXA11 ...

Actually the deployment packages created by .NET will only
install under the Default Web Site as stated by Microsoft.
If you have multiple web sites on the same server (which
is very common), this install package will only install
under the Default Web Site. Yes, you can change the
default web site in IIS but this doesn't work as far
as .NET is concerned.

As I type this I am in communication with 4 different
developers with Microsoft to try and resolve this issue.
I gave in and am using one of are support tickets. As far
as I'm concerned this is a bug and I will not be charged
for the support.

Apparently, many have this problem.
So, when I get the solution, I will take the time to
spread the word.
Until then...
>-----Original Message-----
>I'm not sure I understand the problem. You can deploy ASP.NETapplications >to any instance of web sites on IIS and they will run fine, unlessof course >you've hardcoded something that relies on the default web site
>
>-- PBR.
>
>"Steve" <sd*****@skura.com> wrote in message
>news:00c701c27649$df0a7590$9de62ecf@tkmsftngxs01. ..
>> How? Please someone must have the answer.
>> It is not uncommon for shops to have web servers with
>> multiple web sites on them. Multiple websites with
>> individual IP's, same port...
>>
>> Microsoft are you listening?
>> This is extremely important becasue a Partner this will be
>> the stopper for us to pursue anymore .NET devlopment.
>> Simply copying files won't when you're developing complex
>> web applications.
>>
>> A urgent reply is necessary.
>> Replys may go here and/or to the above email address.
>> Thanks.
>>
>
>
>.

----
Elizabeth Newman – Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.

[Marcus]

Thanks, Elizabeth

We are using VS2002. I called Microsoft yesterday and the person I
spoke with emailed me a patch (it is not available online). It
involves replacing a dll in the deployment directory of Visual Studio,
building the deployment project to create the msi file, and then
running a javascript file called "enablehostheaders.js" with the name
of the MSI file just built as a command argument. This changes the msi
so that when you run it you will get an option asking you what web
site you want to deploy your site to.

Too bad this isn't more easily available as I am sure many others
would benefit. The guy I dealt with said that it will be available
soon, but that they were just waiting for the web documention to be
written.

If anyone would like these files and the instructions passed on from
MS, email me at:

marcus.bell@ec DOT gc DOT ca

Cheers,
Marcus
en*****@online.microsoft.com (Elizabeth Newman [MS]) wrote in message news:<RA**************@cpmsftngxa07.phx.gbl>...

Marcus,

A patch has been created for Visual Studio 2003 to fix this problem. Please call PSS and ask for the "Web Setup patch." If you have any problems, please feel free to give my name to the
support technition.

Hope this helps,
Elizabeth Newman

--------------------

From: ho**********@hotmail.com (Marcus)
Newsgroups: microsoft.public.dotnet.framework.aspnet,microsoft .public.vsnet.setup
Subject: Deploy Asp.Net site when multiple sites exist on server
Date: 16 Feb 2004 17:43:44 -0800
Organization: http://groups.google.com
Lines: 97
Message-ID: <17**************************@posting.google.com >
NNTP-Posting-Host: 199.212.20.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1076982224 5074 127.0.0.1 (17 Feb 2004 01:43:44 GMT)
X-Complaints-To: gr**********@google.com
NNTP-Posting-Date: Tue, 17 Feb 2004 01:43:44 +0000 (UTC)
Path: cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTN GP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!newsfeed.icl.net!ne wsfeed.fjserv.net!nx02.iad01.newshosting.com!

newshosting.com!elnk-atl-nf1!newsfeed.earthlink.net!border2.nntp.ash.gigane ws.com!border1.nntp.ash.giganews.com!nntp.giganews .com!news.maxwell.syr.edu!postnews1.google.com!not-
for-mail

Xref: cpmsftngxa07.phx.gbl microsoft.public.vsnet.setup:4678 microsoft.public.dotnet.framework.aspnet:210664
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

I have seen many posts of people with the same problem as me (attached
below), but I have yet to see any solutions posted. Has anyone figured
out how to deploy an Asp.net web site to the webserver in any place
other than the default website? I do not want to install it there as
our IIS has multiple websites, but nowhere is there an option when
creating the install package in Visual Studio to specify what website
on the server you want to install to. I am using VS 2002.

Anyone?

Thanks,
Marcus
From: Steve (sd*****@skura.com)
Subject: Re: Deployment to NON-default website?
View: Complete Thread (5 articles)
Original Format
Newsgroups: microsoft.public.dotnet.framework.aspnet
Date: 2002-10-22 07:54:39 PST
With regards to my original post, Microsoft has confirmed
this to be a bug. Let's hope they get this fixed in the
next service release.

-----Original Message-----
Steve,

I think you are talking about the deployment packages created by VisualStudio.Net. No "deployment packages" are created by ".Net". It is true thatcurrently the prefab ASP.Net installer created by VS.Net will only deploy tothe default website, but there is nothing stopping you from from creatingyour own installer that will create a new website in IIS and setting up yourapplication there. You might want to check into the ADSI groups for info onhow to do this. Sample scripts and documentation are provided with IIS.
-- PBR

"Steve" <sd*****@skura.com> wrote in message
news:733801c276d6$866dfff0$35ef2ecf@TKMSFTNGXA11 ...
Actually the deployment packages created by .NET will only
install under the Default Web Site as stated by Microsoft.
If you have multiple web sites on the same server (which
is very common), this install package will only install
under the Default Web Site. Yes, you can change the
default web site in IIS but this doesn't work as far
as .NET is concerned.

As I type this I am in communication with 4 different
developers with Microsoft to try and resolve this issue.
I gave in and am using one of are support tickets. As far
as I'm concerned this is a bug and I will not be charged
for the support.

Apparently, many have this problem.
So, when I get the solution, I will take the time to
spread the word.
Until then...
>-----Original Message-----
>I'm not sure I understand the problem. You can deploy ASP.NET applications >to any instance of web sites on IIS and they will run fine, unless of course >you've hardcoded something that relies on the default web site
>
>-- PBR.
>
>"Steve" <sd*****@skura.com> wrote in message
>news:00c701c27649$df0a7590$9de62ecf@tkmsftngxs01. ..
>> How? Please someone must have the answer.
>> It is not uncommon for shops to have web servers with
>> multiple web sites on them. Multiple websites with
>> individual IP's, same port...
>>
>> Microsoft are you listening?
>> This is extremely important becasue a Partner this will be
>> the stopper for us to pursue anymore .NET devlopment.
>> Simply copying files won't when you're developing complex
>> web applications.
>>
>> A urgent reply is necessary.
>> Replys may go here and/or to the above email address.
>> Thanks.
>>
>
>
>.

----
Elizabeth Newman ? Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.