Thanks for your followup Thom,
For multiple application deployment, I agree that nested applications will
be more difficult since the parent application's configuration setting may
affect the sub applications. For such parent/sub deployment, we need to
have well plan and consideration at design-time, otherwise, it'll be better
to arrange them as separate or parallel level application (in IIS virtual
dirs...).
Also, it's also a problem that you can not directly manage the remote site
which make it a bit hard for us to directly throubleshoot the problem and
do furhter research....
In addition, for Master page, we can put different Master pages in
different sub directories and reference them in other pages in different
directory structure (as long as they're in the same web application). e.g:
MasterPageFile="~/MasterPages/SubMaster/submain.master"
The following page reference a Masterpage in the two level nested sub
directories.... We generally specify master page path from the application
root ( "~/xxxxxx/xxxx")... In other words, sub directory pages can
referece Master pages in root application directory, Root dir pages also
able to reference Master pages in sub directory......
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| From: "Thom Little" <th**@tlanet.net>
| References: <#5**************@TK2MSFTNGP09.phx.gbl>
<Uf**************@TK2MSFTNGXA02.phx.gbl>
<e1*************@TK2MSFTNGP14.phx.gbl>
<Q3**************@TK2MSFTNGXA02.phx.gbl>
<vk*************@TK2MSFTNGXA02.phx.gbl>
| Subject: Re: More than One
| Date: Tue, 27 Dec 2005 08:41:33 -0500
| Lines: 327
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eh**************@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: 65.99.185.176
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP11.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:367137
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| I backed away from it slightly. I have a sandbox server and can put an
| application in the root and remove it and successfully replace it with
| another.
|
| I have not got a second application to run in a subdirectory yet.
|
| It is very easy to put the webspace in a "hung" state. One way is to
have
| an application in the root and then publish a second application to the
| root. This almost always hangs the webspace. You must delete the files,
| wait a bit, and then publish the second website in order to avoid the
| problem.
|
| I do not have administrator privilege on the remote server and have to
wait
| for the kindness of others to do the reset. Perhaps I can get
administrator
| privilege limited to this webspace?
|
| I have been investigating master pages. It seems that the master page
MUST
| be in the root of the website. This seems to say that I can't have
| subdirectories with their own master page.
|
| My current assessment is that the environment is quire fragile.
|
| --
| -- Thom Little --
www.tlanet.net -- Thom Little Associates, Ltd.
| --
|
| "Steven Cheng[MSFT]" <st*****@online.microsoft.com> wrote in message
| news:vk*************@TK2MSFTNGXA02.phx.gbl...
| > Hi Thom,
| >
| > Any further progress on this or does those thing in my last reply also
| > helps a little?
| > If still anything else we can help, please feel free to post here.
| >
| > Regards,
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > Get Secure!
www.microsoft.com/security
| > (This posting is provided "AS IS", with no warranties, and confers no
| > rights.)
| > --------------------
| > | X-Tomcat-ID: 65443529
| > | References: <#5**************@TK2MSFTNGP09.phx.gbl>
| > <Uf**************@TK2MSFTNGXA02.phx.gbl>
| > <e1*************@TK2MSFTNGP14.phx.gbl>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain
| > | Content-Transfer-Encoding: 7bit
| > | From:
st*****@online.microsoft.com (Steven Cheng[MSFT])
| > | Organization: Microsoft
| > | Date: Wed, 21 Dec 2005 03:39:41 GMT
| > | Subject: Re: More than One
| > | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| > | Message-ID: <Q3**************@TK2MSFTNGXA02.phx.gbl>
| > | Newsgroups: microsoft.public.dotnet.framework.aspnet
| > | Lines: 209
| > | Path: TK2MSFTNGXA02.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.dotnet.framework.aspnet:366148
| > | NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
| > |
| > | Thanks for your response Thom,
| > |
| > | For common ASP.NET web application(1.1 or 2.0), it's still ok that we
| > | deploy the application by simply copy the page files to the target
| > virtual
| > | directory and assemblies to the target bin folder (if strong-named
| > assembly
| > | , we need to put them into GAC.....).
| > |
| > | I am hoping to have a similar arrangement with 2.0 where there will
32
| > | subdirectories from the root and each will be a separate customer with
| > | separate access controls.
| > | ==============================
| > | I think it possible, since we can just create 32 separate application
| > | virtual directory under the root webspace) and each application
virtual
| > | directory can has its own virtual directory based IIS
| > | setting.....(authentication mode...... )
| > |
| > |
| > |
| > | One difference that I noticed and am still trying to work through is
| > that
| > | there is no namespace statement in ASP.NET 2.0 applications and there
is
| > in
| > | ASP.NET 1.1 applications. Perhaps this is what was providing the nice
| > | segregation of applications in 1.1?
| > | ===============================
| > | No, this won't affect the isolation of each asp.net web application.
| > | No-namespace in asp.net 2.0 is because all the web page classes
| > | or source files in (app_code folder) are dynamically compiled at
| > runtime,
| > | so they will be given a runtime generated internal namespace.... this
| > not
| > | controled by us. And for each web application,their assemblies will be
| > | loaded into their own AppDomain so classes in differernt application
| > won't
| > | conflict with those in other application.....
| > |
| > | Thanks,
| > |
| > | Steven Cheng
| > | Microsoft Online Support
| > |
| > | Get Secure!
www.microsoft.com/security
| > | (This posting is provided "AS IS", with no warranties, and confers no
| > | rights.)
| > |
| > |
| > |
| > | --------------------
| > | | From: "Thom Little" <th**@tlanet.net>
| > | | References: <#5**************@TK2MSFTNGP09.phx.gbl>
| > | <Uf**************@TK2MSFTNGXA02.phx.gbl>
| > | | Subject: Re: More than One
| > | | Date: Tue, 20 Dec 2005 03:08:18 -0500
| > | | Lines: 149
| > | | X-Priority: 3
| > | | X-MSMail-Priority: Normal
| > | | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| > | | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| > | | X-RFC2646: Format=Flowed; Original
| > | | Message-ID: <e1*************@TK2MSFTNGP14.phx.gbl>
| > | | Newsgroups: microsoft.public.dotnet.framework.aspnet
| > | | NNTP-Posting-Host: 65.99.185.176
| > | | Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP14.phx.gbl
| > | | Xref: TK2MSFTNGXA02.phx.gbl
| > | microsoft.public.dotnet.framework.aspnet:365884
| > | | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| > | |
| > | | Thank you for the information. I am still working my way through
it.
| > | |
| > | | In pre-ASP and ASP 3 I worked with a customer by developing a
website
| > on
| > | my
| > | | remote space (currently containing my applications and 37 customer
| > | | applications that have limited access. When the customer is happy
| > with
| > | the
| > | | result I simply copy the "space" from my remote server to the root
of
| > | their
| > | | remote server "webspace" and it is published to the world.
| > | |
| > | | I am hoping to have a similar arrangement with 2.0 where there will
| > 32
| > | | subdirectories from the root and each will be a separate customer
with
| > | | separate access controls.
| > | |
| > | | One difference that I noticed and am still trying to work through is
| > that
| > | | there is no namespace statement in ASP.NET 2.0 applications and
there
| > is
| > | in
| > | | ASP.NET 1.1 applications. Perhaps this is what was providing the
nice
| > | | segregation of applications in 1.1?
| > | |
| > | | --
| > | | -- Thom Little --
www.tlanet.net -- Thom Little Associates,
Ltd.
| > | | --
| > | |
| > | | "Steven Cheng[MSFT]" <st*****@online.microsoft.com> wrote in message
| > | | news:Uf**************@TK2MSFTNGXA02.phx.gbl...
| > | | > Hi Thom,
| > | | >
| > | | > Welcome.
| > | | > As for ASP.NET 2.0 web application hosting in IIS website, it has
| > the
| > | same
| > | | > model as ASP.NET 1.1. Each asp.net web application should reside
in
| > a
| > | | > single virtual directory which is configured as "Application"(have
| > | | > application name....). And for a single asp.net application, it
can
| > | | > contains other sub dirs(normal virutal dir ,not application dir)
| > which
| > | | > contains pages or other static resources... , however, all the
| > | assemblies
| > | | > should be put in the private "bin" dir of the Application's root
| > | | > directory(must...).
| > | | >
| > | | > Also, when hosting multiple asp.net web application, and those
| > | | > applications's diretory has sub/children hierarchy, we need to pay
| > | | > attention for somethings:
| > | | >
| > | | > 1. For web.config, each application's runtime configuration
| > collection
| > | are
| > | | > calculated from the whole hierarchy from its own web.config , to
sub
| > | | > virtual dir's web.config or IIS site root's web.config(if exists)
| > and
| > | | > finally, global web.config(or machine.config....). So if we
defined
| > some
| > | | > application specific data in the super application's web.config,
| > it'll
| > | be
| > | | > inherited in sub application....
| > | | >
| > | | > /siteroot
| > | | > /bin
| > | | > page files....
| > | | > web.config
| > | | >
| > | | >
| > | | > /superwebapp
| > | | > /bin
| > | | > super web app pages.....
| > | | > web.config
| > | | >
| > | | >
| > | | > /sub app
| > | | > /bin
| > | | > sub app pages....
| > | | > web.conifg
| > | | >
| > | | >
| > | | >
| > | | > 2. For some component (such as http handler or httpModule . or
other
| > | | > assembly related setting ) setting in web.config, it'll require we
| > | specify
| > | | > the assembly name.... , in such cases, we need to pay more
| > attention,
| > | | > since
| > | | > the sub applcation will inherit these setting, so at runtime, the
| > sub
| > | | > application will try looking for those assemblies in their own
| > private
| > | | > "bin" folder rather than super application's "bin" dir, this is a
| > common
| > | | > problems ......
| > | | >
| > | | > So generally, we suggest deploy separate applications (haven't
| > | particular
| > | | > super/children relationship) in separate virtual directory path
| > .....
| > | | > If we do have to deploy different applications in virtual
directorys
| > | that
| > | | > have parent/child structure, we need to pay attention to the above
| > | things
| > | | > I
| > | | > mentioned....
| > | | >
| > | | > Here are some msdn reference discussing about ASP.NET web
| > configuration
| > | | > structure/hierarchy and configuration ASP.NET application in IIS:
| > | | >
| > | | > #ASP.NET Configuration File Hierarchy and Inheritance
| > | | >
http://msdn2.microsoft.com/en-us/library/ms178685.aspx
| > | | >
| > | | > #ASP.NET and IIS Configuration
| > | | >
http://msdn2.microsoft.com/en-us/lib...US,VS.80).aspx
| > | | >
| > | | > Hope helps. Thanks,
| > | | >
| > | | > Steven Cheng
| > | | > Microsoft Online Support
| > | | >
| > | | > Get Secure!
www.microsoft.com/security
| > | | > (This posting is provided "AS IS", with no warranties, and
confers
| > no
| > | | > rights.)
| > | | >
| > | | >
| > | | > --------------------
| > | | > | From: "Thom Little" <th**@tlanet.net>
| > | | > | Subject: More than One
| > | | > | Date: Mon, 19 Dec 2005 15:05:45 -0500
| > | | > | Lines: 22
| > | | > | X-Priority: 3
| > | | > | X-MSMail-Priority: Normal
| > | | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| > | | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| > | | > | X-RFC2646: Format=Flowed; Original
| > | | > | Message-ID: <#5**************@TK2MSFTNGP09.phx.gbl>
| > | | > | Newsgroups: microsoft.public.dotnet.framework.aspnet
| > | | > | NNTP-Posting-Host: 65.99.185.176
| > | | > | Path:
| > TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP09.phx.gbl
| > | | > | Xref: TK2MSFTNGXA02.phx.gbl
| > | | > microsoft.public.dotnet.framework.aspnet:365783
| > | | > | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| > | | > |
| > | | > | Visual Studio 2003 / .NET Framework 1.1 I could create multiple
| > web
| > | | > | applications. In the root of a remote webspace I could have a
| > single
| > | | > /bin
| > | | > | directory and a single web.config file.
| > | | > |
| > | | > | I would then FTP (using a third-party FTP program) the .aspx
files
| > in
| > | | > any
| > | | > of
| > | | > | the applications to any directory in the webspace. I would also
| > FTP
| > | all
| > | | > the
| > | | > | .dll files to the single /bin directory in the root.
| > | | > |
| > | | > | Visual Studio 2005 / .NET Framework 2.0 does not seem to support
| > | | > multiple
| > | | > | independent applications in the same webspace
| > | | > |
| > | | > | How can I publish multiple applications (that are built in
| > separate
| > | | > | unconnected projects) in the same webspace?
| > | | > |
| > | | > | Is there a document that describes this procedure that I can
| > access?
| > | | > |
| > | | > | --
| > | | > | -- Thom Little --
www.tlanet.net -- Thom Little Associates,
| > Ltd.
| > | | > | --
| > | | > |
| > | | > |
| > | | > |
| > | | > |
| > | | >
| > | |
| > | |
| > | |
| > |
| > |
| >
|
|
|
