Re: Deploying ASP.NET Application
From: John Oakes (john_at_networkproductions.net)
Date: 02/13/04
- Next message: John Oakes: "Re: System.Diagnostics, Process and Security"
- Previous message: Saravana [MVP]: "Re: Forms autentication and registration page - some advices"
- In reply to: Steve: "Re: Deploying ASP.NET Application"
- Next in thread: Elizabeth Newman [MS]: "Re: Deploying ASP.NET Application"
- Reply: Elizabeth Newman [MS]: "Re: Deploying ASP.NET Application"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Feb 2004 01:26:23 -0500
I don't know if this has changed since I last tried it, but I remember about
a year ago doing this and learning that it only supports installing to the
default instance. I have built several of these installers for webapps and
I finally decided copy project worked much better for me. The limited
convenience the msi created was never enough to compensate for the
drawbacks.
-John
"Steve" <anonymous@discussions.microsoft.com> wrote in message
news:268A5727-2720-4218-A45B-436FB458775A@microsoft.com...
> Scott,
> Thanks for the response. I am installing to another webserver based on IP
Address. However, when I run the msi the only option I get to pick is a
Virtual Directory, I never see anything about picking a port, webserver
instance etc. Do I need to change something in my VS.NET Output Project
that builds the MSI?
>
> Steve
>
> ----- Scott Allen wrote: -----
>
> So you are still trying to deploy to the same machine, but on a
second
> second website? Websites are differentiated by IP address, port or
> host header - do you know which one you picked? For example, if you
> put the second site on port 90, you would want to deply to
>
> http://hostmachine1:90
>
> HTH,
>
> --
> Scott
> http://www.OdeToCode.com
>
> On Thu, 12 Feb 2004 10:21:11 -0800, "Frustrated Developer"
> <anonymous@discussions.microsoft.com> wrote:
>
> >I am trying to deploy my ASP.NET application developed in VS.NET
2003. I have a project which builds my msi. When I run the msi on my local
machine it works great. However, when I take the msi and deploy it to any
other box it doesn't work. For example, my physical production box is name
"hostmachine1". I am not using the Default Web Server on this box, I
created another webserver named "thishostmachine". The first problem was
every time I tried to deploy it always deployed to the default website,
event if I turned it off as instructed. So I deleted the default website
and now when I try to deploy it says "The specified path
http://hostmachine1" is unavailable. I don't want to deploy to
"hostmachine1" I want to deploy to "thishostmachine". It looks like the msi
always wants to deploy to the physical box name, never the other webserver I
setup. Can someone help!!!!!
> >I am using WIN2K SP4 with IIS 5.0
> >>Very Frustrated developer.
>
>
- Next message: John Oakes: "Re: System.Diagnostics, Process and Security"
- Previous message: Saravana [MVP]: "Re: Forms autentication and registration page - some advices"
- In reply to: Steve: "Re: Deploying ASP.NET Application"
- Next in thread: Elizabeth Newman [MS]: "Re: Deploying ASP.NET Application"
- Reply: Elizabeth Newman [MS]: "Re: Deploying ASP.NET Application"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
