I have various domains using the same application/assembly
They differ in contents and design, based on a "site id", and get its
information from an SQL server.
Now I have to deploy the different "sites" to individual folders on the
server, and set up the domains on IIS to point to these folders.
If I do changes in the application, I have to deploy to all the different
folders on the server.
What I want to do is to have one single root web, and let all the domains
point to this in IIS.
Then I have to deploy only once.
The problem is. How do I configure web.config, to allow me to use multiple
domains, sharing a common application and root folder.
6  4835 
You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no... I have various domains using the same application/assembly
They differ in contents and design, based on a "site id", and get its
information from an SQL server.
Now I have to deploy the different "sites" to individual folders on the
server, and set up the domains on IIS to point to these folders.
If I do changes in the application, I have to deploy to all the different
folders on the server.
What I want to do is to have one single root web, and let all the domains
point to this in IIS.
Then I have to deploy only once.
The problem is. How do I configure web.config, to allow me to use multiple
domains, sharing a common application and root folder.
No, deployment isn't that hard, but when the number of sites using the same
application increases, the advantage is clear.
I'm not sure I understood the use of virtual root.
So, there is no way to configure this in web.config, then??
"Patrice" <no****@nowhere.com> skrev i melding
news:OT**************@tk2msftngp13.phx.gbl... You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no... I have various domains using the same application/assembly
They differ in contents and design, based on a "site id", and get its
information from an SQL server.
Now I have to deploy the different "sites" to individual folders on the
server, and set up the domains on IIS to point to these folders.
If I do changes in the application, I have to deploy to all the
different folders on the server.
What I want to do is to have one single root web, and let all the
domains point to this in IIS.
Then I have to deploy only once.
The problem is. How do I configure web.config, to allow me to use
multiple domains, sharing a common application and root folder.
re: The problem is. How do I configure web.config,
to allow me to use multiple domains, sharing a
common application and root folder.
Actually, web.config has nothing to do with that.
You can have as many web.configs as
there are subdirectories of your application.
What you want to do is configure one application
to serve as the source for multiple domains.
Maybe, if you want to run a single application,
in global.asax -in Session_OnStart- you could
sniff/parse the URL coming in, and redirect to
the appropiate domain.
But, ASP.NET was not written with that possibility in mind.
You, generally, work with different applications
when they are hosted in different domains.
Juan T. Llibre
ASP.NET MVP
===========
"Ludvig" <gj******@fastpublish.no> wrote in message
news:UF*********************@news.telia.no... No, deployment isn't that hard, but when the number of sites using the
same
application increases, the advantage is clear.
I'm not sure I understood the use of virtual root.
So, there is no way to configure this in web.config, then??
"Patrice" <no****@nowhere.com> skrev i melding
news:OT**************@tk2msftngp13.phx.gbl... You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no... > I have various domains using the same application/assembly
>
> They differ in contents and design, based on a "site id", and get its
> information from an SQL server.
>
> Now I have to deploy the different "sites" to individual folders on the
> server, and set up the domains on IIS to point to these folders.
> If I do changes in the application, I have to deploy to all the
> different folders on the server.
>
> What I want to do is to have one single root web,
> and let all the domains point to this in IIS.
> Then I have to deploy only once.
>
> The problem is. How do I configure web.config, to allow me to use
> multiple domains, sharing a common application and root folder.
Not sure but you could likely do something like :
- the application root is a directory that is on each and every server, this
way you have a distinct web config file for each
- under the application root you create a virtual that points to your app
single copy
Note that AFAIK 2.0 will allow to deploy a whiole site as as single DLL.
My personal preference would be still to automate deployement on distinct
servers (it could be just a batch) to keep the ability to manage separately
those sites...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:UF*********************@news.telia.no... No, deployment isn't that hard, but when the number of sites using the
same application increases, the advantage is clear.
I'm not sure I understood the use of virtual root.
So, there is no way to configure this in web.config, then??
"Patrice" <no****@nowhere.com> skrev i melding
news:OT**************@tk2msftngp13.phx.gbl... You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no... I have various domains using the same application/assembly
They differ in contents and design, based on a "site id", and get its
information from an SQL server.
Now I have to deploy the different "sites" to individual folders on
the server, and set up the domains on IIS to point to these folders.
If I do changes in the application, I have to deploy to all the different folders on the server.
What I want to do is to have one single root web, and let all the domains point to this in IIS.
Then I have to deploy only once.
The problem is. How do I configure web.config, to allow me to use multiple domains, sharing a common application and root folder.
Tanks
"But, ASP.NET was not written with that possibility in mind.
You, generally, work with different applications
when they are hosted in different domains."
May be this was no good idea after all.
"Juan T. Llibre" <no***********@nowhere.com> skrev i melding
news:em*************@TK2MSFTNGP15.phx.gbl... re: The problem is. How do I configure web.config,
to allow me to use multiple domains, sharing a
common application and root folder.
Actually, web.config has nothing to do with that.
You can have as many web.configs as
there are subdirectories of your application.
What you want to do is configure one application
to serve as the source for multiple domains.
Maybe, if you want to run a single application,
in global.asax -in Session_OnStart- you could
sniff/parse the URL coming in, and redirect to
the appropiate domain.
But, ASP.NET was not written with that possibility in mind.
You, generally, work with different applications
when they are hosted in different domains.
Juan T. Llibre
ASP.NET MVP
===========
"Ludvig" <gj******@fastpublish.no> wrote in message
news:UF*********************@news.telia.no... No, deployment isn't that hard, but when the number of sites using the
same
application increases, the advantage is clear.
I'm not sure I understood the use of virtual root.
So, there is no way to configure this in web.config, then??
"Patrice" <no****@nowhere.com> skrev i melding
news:OT**************@tk2msftngp13.phx.gbl... You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice "Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no...
> I have various domains using the same application/assembly
>
> They differ in contents and design, based on a "site id", and get its
> information from an SQL server.
>
> Now I have to deploy the different "sites" to individual folders on
the > server, and set up the domains on IIS to point to these folders.
> If I do changes in the application, I have to deploy to all the
> different folders on the server.
>
> What I want to do is to have one single root web,
> and let all the domains point to this in IIS.
> Then I have to deploy only once.
>
> The problem is. How do I configure web.config, to allow me to use
> multiple domains, sharing a common application and root folder.
Thanks
I'll give it a try..
"Patrice" <no****@nowhere.com> skrev i melding
news:uL**************@TK2MSFTNGP15.phx.gbl... Not sure but you could likely do something like :
- the application root is a directory that is on each and every server,
this way you have a distinct web config file for each
- under the application root you create a virtual that points to your app
single copy
Note that AFAIK 2.0 will allow to deploy a whiole site as as single DLL.
My personal preference would be still to automate deployement on distinct
servers (it could be just a batch) to keep the ability to manage
separately those sites...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:UF*********************@news.telia.no... No, deployment isn't that hard, but when the number of sites using the
same application increases, the advantage is clear.
I'm not sure I understood the use of virtual root.
So, there is no way to configure this in web.config, then??
"Patrice" <no****@nowhere.com> skrev i melding
news:OT**************@tk2msftngp13.phx.gbl... You could use a virtual root below your main directory and keep a main
directory. That said I would still question the expected benefits.
Is deployement that hard ? Y'oull have now all of your sites tireds...
Patrice
--
"Ludvig" <gj******@fastpublish.no> a écrit dans le message de
news:KV*********************@news.telia.no...
> I have various domains using the same application/assembly
>
> They differ in contents and design, based on a "site id", and get
its > information from an SQL server.
>
> Now I have to deploy the different "sites" to individual folders on the > server, and set up the domains on IIS to point to these folders.
> If I do changes in the application, I have to deploy to all the
different > folders on the server.
>
> What I want to do is to have one single root web, and let all the
domains > point to this in IIS.
> Then I have to deploy only once.
>
> The problem is. How do I configure web.config, to allow me to use
multiple > domains, sharing a common application and root folder.
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: DraguVaso |
last post by:
Hi,
I have a Windows Service running (made in VB.NET), and wanted to be able to
change from time to time some parameters by changing them in the App.config.
But it seems that the application...
|
by: Fred Palmer |
last post by:
Hi all,
Can anyone point out some best practices for handling cookies with multiple
domains aliases?
The problem is that I've got a site with multiple domain aliases and I want
them to all...
|
by: Brett Romero |
last post by:
If my UI app uses three DLLs and two of those DLLs reference something
named utilities.dll, does the UI app load utilities.dll twice or does
the compiler recognize what is going on and load...
|
by: Ricky Romaya |
last post by:
Hi,
I'm using Apache webserver 1.3.27 and PHP 4.3.0. On my development machine,
I have created several virtual hosts. AFAIK PHP configuration is stored in
php.ini. I want some of the virtual...
|
by: mindflower |
last post by:
Hi,
i have a web application running on multiple web domains. I'm looking for
the best way to cache data across these multiple domains. The
System.Web.Caching.Cache only supports caching over a...
|
by: =?Utf-8?B?SmVycnkgQw==?= |
last post by:
I am trying to implement a configuration section in web.config and was
wondering if I could do it without writing a handeler. I tried in the
<configSections>.
<sectionGroup name="Domains" >...
|
by: Samir Chouaieb |
last post by:
Hello,
I am trying to find a solution to a login mechanism for different
domains on different servers with PHP5.
I have one main domain with the user data and several other domains that
need...
|
by: BDE Consulting |
last post by:
I am going crazy. This has been a problem now for over a year and I
have yet to figure out what is causing it.
I have a single server that is running multiple domains. For this
example I will...
|
by: teddarr |
last post by:
I have a Windows Server 2003. I am trying to run multiple websites on the server.
I am using host headers to run the websites on only one ip address.
Before anyone says this is an iis issue and...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| | |
