Hello!

Can run multiple instances of a web application in one IIS or could i get
some problems with them?

Many thanks!

Joerg

How would you address them via url in a browser?
What are you trying to accomplish?

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

I really don't think the concept of "instances" applies in the case of ASP.NET applications. Perhaps this is just a bit of bad terminology on your part, when you actually meant something else.

-Altaf
[MVP]



--------------------------------------------------------------------------------

All that glitters has a high refractive index.
www.mendhak.com
"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> wrote

How would you address them via url in a browser?
What are you trying to accomplish?

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------



"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

Joerg,

I am not sure exactly what you mean. If you mean multiple client (browser)
connections/sessions with a single Web app, then no problem. This is the
"default" setup. If you mean having severeal copies of the same Web app
running on IIS simulteneanously, which I suspect you do, you would at least
a way of "separating" the instances using say a naming convention. I'm not
sure what the purpose is, but perhaps this is related to a Web farm and/or
scalability?

--
Carsten Thomsen
Communities - http://community.integratedsolutions.dk

"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

Hello!

Yes, we have or want to have several copies of a wep app on the iis. I sthis
possible or what you mean with using naming convention.

We wan to use the web app following.

http://ipaddress/WebApp1
http://ipaddress/WebApp2
http://ipaddress/WebApp3

Many thanks,

Joerg
"CT" <carstent (AT) spammersgoawayintegrasol (DOT) dk> wrote

Joerg,

Yes, this is possible. The only question is if you want all of the URLs to
point to the same physical folder, or if you want a copy of the Web app in a
seperate folder for each URL?

--
Carsten Thomsen
Communities - http://community.integratedsolutions.dk

"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

I want have a folder for each web app. For example:

...inetpub/wwwroot/webapp1
...inetpub/wwwroot/webapp2
...inetpub/wwwroot/webapp3

Joerg

"CT" <carstent (AT) spammersgoawayintegrasol (DOT) dk> wrote

Okay, so you want this URL, http://servername/webapp1 to point to the
\inetpub\wwwroot\webapp1 physical folder on disk, http://servername/webapp2
to point to the \inetpub\wwwroot\webapp2 folder, and
http://servername/webapp3 to point to the \inetpub\wwwroot\webapp3 folder,
right? Now, you then need a copy of your code in each of these folders, and
I guess this is where your original question is very valid; can this be
problematic. Yes, it can, depening on which resources your application
accesses. If you access a database, your code should handle concurrency
issues, and you might want to go with optimistic concurrency. Having said
that, any Web application needs to handle concurrency issues as you can have
multiple users online simulteanously. In fact, just about all applications
need to cater for concurrency issues these days. :-)

Now, the problem with the suggested setup is if you have any application
wide settings saved to application state, as this isn't possible across your
different Web apps. Well, at least it isn't possible without some quirks, if
you know what I mean. If you happen to save to a file on disk there are also
potential problems, because of locking issues.

I'm sure there are other things to look out for, but to keep it short, your
idea can work. Now that's out of the way, can you possibly tell me why you
want to do it this way?


--
Carsten Thomsen
Communities - http://community.integratedsolutions.dk

"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote

We need this, because we want to use the webApp for different projects. Each
project should have its own webApp with the own web.config, where for
example the connection string is stored. Each wepApp has its own database.

Joerg

"CT" <carstent (AT) spammersgoawayintegrasol (DOT) dk> wrote

In that case you should be safe with the suggested setup. :-)

--
Carsten Thomsen
Communities - http://community.integratedsolutions.dk

"Joerg Schrocke" <speedy1179 (AT) web (DOT) de> wrote