David
Sat Apr 08 17:22:25 CDT 2006
Go into IIS Manager UI and change the Application name to whatever you want.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Juan T. Llibre" <nomailreplies@nowhere.com> wrote in message
news:eGdVTNxWGHA.2268@TK2MSFTNGP02.phx.gbl...
> Thanks, David. I *had* seen your post.
>
> I already knew all of what you're saying, except the last part.
> Could you explain how you "sync up WebApplication Name with URL" ?
>
>
>
> Juan T. Llibre, asp.net MVP
> aspnetfaq.com :
http://www.aspnetfaq.com/
> asp.net faq :
http://asp.net.do/faq/
> foros de asp.net, en español :
http://asp.net.do/foros/
> ===================================
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:%23z2QcIrWGHA.4972@TK2MSFTNGP02.phx.gbl...
>>- Application Pool Names are unique.
>> - URLs are unique.
>> - WebApplication Name is not unique. It is an arbitrary "friendly name"
>> associated with a given URL. It is like Website "friendly name" vs its
>> Website ID -- Website ID is unique, but "friendly name" is not
>> - Each WebApplication is serviced by exactly one Application Pool.
>>
>> Given the above rules, it is conceivable to have the following
>> configuration:
>> /WebApp1 is named DefaultApplication and associated with DefaultAppPool
>> /WebApp2 is named DefaultApplication and associated with DefaultAppPool
>>
>> This means when you look at DefaultAppPool, you will see
>> DefaultApplication
>> listed twice, once for /WebApp1 and another for /WebApp2
>>
>> Why do we have WebApplication Name? It is a convenient form of
>> indirection
>> for users that want it. However, if it confuses it, sync up
>> WebApplication
>> Name with URL and you should be fine.
>>
>> --
>> //David
>> IIS
>>
http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> "Juan T. Llibre" <nomailreplies@nowhere.com> wrote in message
>> news:OYrq6%23jWGHA.128@TK2MSFTNGP05.phx.gbl...
>>> Thanks, Ken.
>>>
>>> Would there be a rational basis for determining which of
>>> the two "Default Web Applications" should be changed ?
>>>
>>> Or, will changing either suffice ?
>>>
>>> Also, will changing the friendly name of a "Default Web Application"
>>> imply any operational changes ?
>>>
>>>
>>>
>>>
>>> Juan T. Llibre, asp.net MVP
>>> aspnetfaq.com :
http://www.aspnetfaq.com/
>>> asp.net faq :
http://asp.net.do/faq/
>>> foros de asp.net, en español :
http://asp.net.do/foros/
>>> ===================================
>>> "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
>>> news:Ou5g20gWGHA.1564@TK2MSFTNGP03.phx.gbl...
>>>> Then the correct solution is to change the web application name so that
>>>> they
>>>> don't have the same name. This has no impact on the server. Whereas
>>>> moving
>>>> the application to a separate app pool depends on a proper analysis of
>>>> the
>>>> costs/benefits involved.
>>>>
>>>> Cheers
>>>> Ken
>>>>
>>>> --
>>>> IIS Blog:
http://www.adOpenStatic.com/cs/blogs/ken
>>>>
>>>> "Juan T. Llibre" <nomailreplies@nowhere.com> wrote in message
>>>> news:OonL70cWGHA.4580@TK2MSFTNGP04.phx.gbl...
>>>> : re:
>>>> : > It is also perfectly valid to have applications with the same name,
>>>> in
>>>> the same application pool.
>>>> :
>>>> : It's quite valid, alright. The thing is, it's also quite confusing.
>>>> :
>>>> : Why would anyone want to have confusing IIS data ?
>>>> :
>>>> :
>>>> :
>>>> : Juan T. Llibre, asp.net MVP
>>>> : aspnetfaq.com :
http://www.aspnetfaq.com/
>>>> : asp.net faq :
http://asp.net.do/faq/
>>>> : foros de asp.net, en español :
http://asp.net.do/foros/
>>>> : ===================================
>>>> : "Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
>>>> : news:xn0ekojknefi5l500m@news.microsoft.com...
>>>> : > Foolish to solve a cosmetic thing, with no affect whatsoever on the
>>>> server, by using something
>>>> : > that do affect the server. It is also perfectly valid to have
>>>> applications with the same name, in
>>>> : > the same application pool.
>>>> : >
>>>> : >
>>>> : > --
>>>> : > Regards,
>>>> : > Kristofer Gafvert
>>>> : >
http://www.gafvert.info/iis/ - IIS Related Info
>>>> : >
>>>> : >
>>>> : > Juan T. Llibre wrote:
>>>> : >
>>>> : >>re:
>>>> : >>>You cannot make a general comment such as "you should setup
>>>> different
>>>> AppPools for each website".
>>>> : >>
>>>> : >>If the OP doesn't want an AppPool to contain
>>>> : >>two applications named "Default Application", I sure can.
>>>> : >>
>>>> : >>;-)
>>>> : >>
>>>> : >>Otherwise, sure.
>>>> : >>
>>>> : >>
>>>> : >>
>>>> : >>Juan T. Llibre, asp.net MVP
>>>> : >>aspnetfaq.com :
http://www.aspnetfaq.com/
>>>> : >>asp.net faq :
http://asp.net.do/faq/
>>>> : >>foros de asp.net, en español :
http://asp.net.do/foros/
>>>> : >>===================================
>>>> : >>"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
>>>> : >>news:xn0eko2fse9flub00i@news.microsoft.com...
>>>> : >>>You cannot make a general comment such as "you shold setup
>>>> different
>>>> AppPools for each website".
>>>> : >>>Whether to use one application pool for multiple websites or one
>>>> for
>>>> each website is dependent on
>>>> : >>>a series of factors. For example in a shared hosting environment
>>>> you
>>>> want all static websites in
>>>> : >>>the same application pool because it will consume less resources,
>>>> and a
>>>> static website is
>>>> : >>>unlikely to crash the application pool.
>>>> : >>>
>>>> : >>>You will need to evaluate the advantages and disadvantages of
>>>> multiple
>>>> application pools, and
>>>> : >>>based on that decide to use multiple application pools or not (in
>>>> your
>>>> specific situation).
>>>> : >>>
>>>> : >>>-- Regards,
>>>> : >>>Kristofer Gafvert
>>>> : >>>
http://www.gafvert.info/iis/ - IIS Related Info
>>>> : >>>
>>>> : >>>
>>>> : >>>Juan T. Llibre wrote:
>>>> : >>>
>>>> : >>>>You will have one Default Application for every website.
>>>> : >>>>Other applications will derive from the Default Application for
>>>> each
>>>> website.
>>>> : >>>>
>>>> : >>>>You should setup different AppPools for each website, at least.
>>>> : >>>>
>>>> : >>>>
>>>> : >>>>
>>>> : >>>>Juan T. Llibre, asp.net MVP
>>>> : >>>>aspnetfaq.com :
http://www.aspnetfaq.com/
>>>> : >>>>asp.net faq :
http://asp.net.do/faq/
>>>> : >>>>foros de asp.net, en español :
http://asp.net.do/foros/
>>>> : >>>>===================================
>>>> : >>>>"John A Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
>>>> : >>>>news:O9iDvyaWGHA.4620@TK2MSFTNGP04.phx.gbl...
>>>> : >>>>>On WS03 how is it possible that an AppPool can contain two
>>>> applications named
>>>> : >>>>>"DefaultApplication" ?
>>>> :
>>>> :
>>>>
>>>>
>>>
>>>
>>
>>
>
>