The "shared dll" part is easy to accomplish.
Just install your common assembly to the machine's GAC.
Re shared variables, your best bet is storing them in a database,
where they can be accessed by anybody you want to allow access to.
re:
> there must be a payload with using a database rather than memory.
You could always have the original data in the database,
so that only the initial hit will generate a payload,
and use the Cache object to store your data in memory.
Using a SQL Cache dependency will allow you
to re-hit the database if the data has changed.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
> Hi
>
[quoted text clipped - 21 lines]
>
> Alex
postings@alexshirley.com - 20 Jul 2005 11:51 GMT
Thanks Juan.
I am wondering what would happen in a web hosting provider situation.
They can provide shared hosting on the Windows 2003 server to a number
of customers holding websites. Installing a common assembly into the
machine's GAC means that any other person holding a website on that
server will have access to my code. Also some of my websites may be
held on different web servers, can a GAC be made available, say, by
Active directory or some other technology? The other alternative is to
rent a standand alone server from the hosting provider, but this of
course is far more expensive.
Many Thanks!
Alex