>I have a web server that is running several ASP.NET projects. I have one .dll I am going to eventually make available to multiple applications on the web server. What would be the best way to do this? Logic tells me to put it in one location on the server, and have the multiple projects point at the same file, but I am not sure how to implement this.
>
>A web service would be preferrable, but I don't think that will be possible.

I am not sure it is a good idea to have one DLL to be shared across multiple applications. In my case, I have one Framework.DLL file that is used on all applications. However, I copy that file in the Bin directory of each Web site. By that, if I update the file, and decide to try it on one Web site, then the others will continue to run as is. Also, by that, I can be sure that all components required by the applications are all under the same root. So, it is much easier for maintenance and moving Web site from one location to another, when applicable, and if applicable.