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

How to deploy 2 distinct ASP.NET apps with one in V.Dir and one in site root

P: n/a
I have two completely distinct ASP.NET (2.0) web applications. They share no
code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be run
through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of
the dotnetnuke app, because dotnetnuke is in the root of the site. How can I
make them live as distinct applications again, but keep the address of the
dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS websites,
but the server only has 1 IP address.
May 22 '06 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Have you tried to declare http://www.company.co.uk/phone as an IIS
application ? AFAIK it should allows to prevent buulling up to the root
web.condfig...

--

"news.microsoft.com" <la*************@hotmail.com> a écrit dans le message
de news: u5**************@TK2MSFTNGP02.phx.gbl...
I have two completely distinct ASP.NET (2.0) web applications. They share
no
code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be
run
through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of
the dotnetnuke app, because dotnetnuke is in the root of the site. How can
I
make them live as distinct applications again, but keep the address of the
dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS
websites,
but the server only has 1 IP address.

May 22 '06 #2

P: n/a
Yes, at least I think so. In IIS the phone app is in a Virtual Directory
called "phone" and if I look at the properties of the Virtual Directory, the
Application Name is MobilePhone, whereas the website root has an Application
Name of DotNetNuke.
"Patrice" <sc****@chez.com> wrote in message
news:eH****************@TK2MSFTNGP05.phx.gbl...
Have you tried to declare http://www.company.co.uk/phone as an IIS
application ? AFAIK it should allows to prevent buulling up to the root
web.condfig...

--

"news.microsoft.com" <la*************@hotmail.com> a écrit dans le message
de news: u5**************@TK2MSFTNGP02.phx.gbl...
I have two completely distinct ASP.NET (2.0) web applications. They share
no
code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be
run
through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of the dotnetnuke app, because dotnetnuke is in the root of the site. How can I
make them live as distinct applications again, but keep the address of the dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS
websites,
but the server only has 1 IP address.


May 22 '06 #3

P: n/a
> I have two completely distinct ASP.NET (2.0) web applications. They share no
code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be run
through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of
the dotnetnuke app, because dotnetnuke is in the root of the site. How can I
make them live as distinct applications again, but keep the address of the
dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS websites,
but the server only has 1 IP address.


You can have two applications for the same IP address, using different
hostnames.
www.company.co.uk your dotnetnuke app
phone.company.co.uk your mobilephone app

And the apps can live in different directories. No need to have your
phone app in a physical subdirectory of your root.
Now that I think of that, maybe that's also a solution: install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

Hans Kesting
May 22 '06 #4

P: n/a
I didn't follow what you said:
install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

.... but the method for creating multiple sites on 1 IP sounds promising.
This is using the 'host headers' function in IIS to distinguish different
sites on the same IP right?

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I have two completely distinct ASP.NET (2.0) web applications. They share no code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be run through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of the dotnetnuke app, because dotnetnuke is in the root of the site. How can I make them live as distinct applications again, but keep the address of the dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS websites, but the server only has 1 IP address.


You can have two applications for the same IP address, using different
hostnames.
www.company.co.uk your dotnetnuke app
phone.company.co.uk your mobilephone app

And the apps can live in different directories. No need to have your
phone app in a physical subdirectory of your root.
Now that I think of that, maybe that's also a solution: install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

Hans Kesting

May 22 '06 #5

P: n/a
> I didn't follow what you said:
install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there. ... but the method for creating multiple sites on 1 IP sounds promising.
This is using the 'host headers' function in IIS to distinguish different
sites on the same IP right?


Correct, host headers let you have multiple "root sites" on a single
IP-address/IIS

and with installing "next to" I meant:
install the root-app in D:\websites\root
and the phone-app in D:\websites\phone

(and maybe add a virtual directory to the root-app, pointing to phone)

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I have two completely distinct ASP.NET (2.0) web applications. They share
no code, they have distinct web.config files, they don't even link to each
other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I
want the first app to be run through the site root and the second to be run
through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

My problem is, with this setup, the mobilephoneapp uses the web.config of
the dotnetnuke app, because dotnetnuke is in the root of the site. How can
I make them live as distinct applications again, but keep the address of
the dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS
websites, but the server only has 1 IP address.


You can have two applications for the same IP address, using different
hostnames.
www.company.co.uk your dotnetnuke app
phone.company.co.uk your mobilephone app

And the apps can live in different directories. No need to have your
phone app in a physical subdirectory of your root.
Now that I think of that, maybe that's also a solution: install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

Hans Kesting

May 22 '06 #6

P: n/a
OK thanks, but is there any way to have both applications live within the
same site, like this?

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

Doesn't using host headers mean that each root site must have a separate
host name?

Laurence
"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I didn't follow what you said:
install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

... but the method for creating multiple sites on 1 IP sounds promising.
This is using the 'host headers' function in IIS to distinguish different sites on the same IP right?


Correct, host headers let you have multiple "root sites" on a single
IP-address/IIS

and with installing "next to" I meant:
install the root-app in D:\websites\root
and the phone-app in D:\websites\phone

(and maybe add a virtual directory to the root-app, pointing to phone)

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I have two completely distinct ASP.NET (2.0) web applications. They share no code, they have distinct web.config files, they don't even link to each other. During development, they have lived happily side by side in two
virtual directories in the same IIS website.

e.g. http://localhost/dotnetnuke
and http://localhost/mobilephoneapp

Now they are ready to be deployed to a production webserver (IIS 6.0). I want the first app to be run through the site root and the second to be run through a virtual directory:

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app
My problem is, with this setup, the mobilephoneapp uses the web.config of the dotnetnuke app, because dotnetnuke is in the root of the site. How can I make them live as distinct applications again, but keep the address of the dotnetnuke app as http://www.company.co.uk?

FYI, I know I might be able to accomplish this by creating two IIS
websites, but the server only has 1 IP address.

You can have two applications for the same IP address, using different
hostnames.
www.company.co.uk your dotnetnuke app
phone.company.co.uk your mobilephone app

And the apps can live in different directories. No need to have your
phone app in a physical subdirectory of your root.
Now that I think of that, maybe that's also a solution: install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

Hans Kesting


May 22 '06 #7

P: n/a
> OK thanks, but is there any way to have both applications live within the
same site, like this?

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

Doesn't using host headers mean that each root site must have a separate
host name?

Laurence
True.
Try for a "mixed" solution: install the apps in side-by-side
directories
(I *think* that the merging of web.config's goes by *physical*
directory
hierarchy) and have a virtual directory in "root" point to "phone".

Hans Kesting


"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I didn't follow what you said:
install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.
... but the method for creating multiple sites on 1 IP sounds promising.
This is using the 'host headers' function in IIS to distinguish different
sites on the same IP right?


Correct, host headers let you have multiple "root sites" on a single
IP-address/IIS

and with installing "next to" I meant:
install the root-app in D:\websites\root
and the phone-app in D:\websites\phone

(and maybe add a virtual directory to the root-app, pointing to phone)

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...

You can have two applications for the same IP address, using different
hostnames.
www.company.co.uk your dotnetnuke app
phone.company.co.uk your mobilephone app

And the apps can live in different directories. No need to have your
phone app in a physical subdirectory of your root.
Now that I think of that, maybe that's also a solution: install your
phone app in a directory *next to* the root-app (instead of below it)
and have a virtual directory from the root point there.

Hans Kesting

May 22 '06 #8

P: n/a
I have the two applications in separate physical directories and the problem
still occurs.
ASP.NET seems to use a hierachy based on virtual directories, not physical
directories. I found this explanation:
http://www.microsoft.com/technet/pro....mspx?mfr=true

It doesn't look like I can resolve this as planned. Thanks for your help.

"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
OK thanks, but is there any way to have both applications live within the same site, like this?

e.g. http://www.company.co.uk <--- this is the dotnetnuke app
and http://www.company.co.uk/phone <--- this is the mobilephoneapp app

Doesn't using host headers mean that each root site must have a separate
host name?

Laurence


True.
Try for a "mixed" solution: install the apps in side-by-side
directories
(I *think* that the merging of web.config's goes by *physical*
directory
hierarchy) and have a virtual directory in "root" point to "phone".

Hans Kesting


"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
I didn't follow what you said:
> install your
> phone app in a directory *next to* the root-app (instead of below it)
> and have a virtual directory from the root point there.
... but the method for creating multiple sites on 1 IP sounds promising. This is using the 'host headers' function in IIS to distinguish different sites on the same IP right?

Correct, host headers let you have multiple "root sites" on a single
IP-address/IIS

and with installing "next to" I meant:
install the root-app in D:\websites\root
and the phone-app in D:\websites\phone

(and maybe add a virtual directory to the root-app, pointing to phone)
"Hans Kesting" <ne***********@spamgourmet.com> wrote in message
news:mn***********************@spamgourmet.com...
>
> You can have two applications for the same IP address, using different> hostnames.
> www.company.co.uk your dotnetnuke app
> phone.company.co.uk your mobilephone app
>
> And the apps can live in different directories. No need to have your
> phone app in a physical subdirectory of your root.
> Now that I think of that, maybe that's also a solution: install your
> phone app in a directory *next to* the root-app (instead of below it)
> and have a virtual directory from the root point there.
>
> Hans Kesting


May 23 '06 #9

This discussion thread is closed

Replies have been disabled for this discussion.