I have a bunch of websites that use the same pictures. I want all there websites to draw from the same foler which will make the administration of the pictures easier. All the sites are hosted on the same server.

How do I get the pictures for all sites from this one folder?
If I use the absolute path: file:///C:/website/files/2011/logos/2018.gif is just displays nothing and if I use this path it shows a broken link:
C:/website/files/2011/logos/2018.gif

I have checked the spelling and everything is 100%
If I copy the file that is requesting these pictures outside of the applications root it gets the file fine.
This is a asp.net application.

So my question again. How do I get the pictures for all sites from this one folder?

It may be a security issue involving user rights. The easy and safe way to accomplish what you want is to choose a web site as the host for the picture and put your image in the Images folder. Then reference regularly from that website. The other web sites can get the picture by useing the website path such as http://www.yoursite.com/images/yourpic.jpg . This is how most people recycle images.

I hope that this helps you.

add a virutal folder to all you apps that point to the same images folder.
reference the images from the virtual folder

brianparker wrote:

The other web sites can get the picture by useing the website path such as http://www.yoursite.com/images/yourpic.jpg . This is how most people recycle images. I hope that this helps you.

I just want to ask one question in doing it this way. Is it not slower to access the pictures this way? If it is slower is it much slower or only a little slower?

You should not notice a difference.

Thanks a lot. I wanted to do it that way at first but thought it would make a speed difference.

If you are concerned about speed than take a look at Output caching. You can cache your images so the new user will see the images returned to him from the cache.

testvoid wrote:

Thanks a lot. I wanted to do it that way at first but thought it would make a speed difference.

No, as Brian mentioned, you won't notice a speed difference, because it's not slower at all.  It'll be exactly the same as if you were using a relative path to the same directory.  There's no need to do anything special at all.

azamsharp wrote:

If you are concerned about speed than take a look at Output caching. You can cache your images so the new user will see the images returned to him from the cache.

That's not how output caching works.  Output caching caches compiled ASP.Net pages, *not* images, which are retrieved via seperate HTTP requests that the browser is making after it's gotten the page. 

Thanks for correcting me. However you can cache the images using your webserver.

For that check out this post: http://forums.asp.net/971043/ShowPost.aspx

azamsharp wrote:

Thanks for correcting me. However you can cache the images using your webserver. For that check out this post: http://forums.asp.net/971043/ShowPost.aspx

True, but note that that's really most relevant for images that are changing.  Images that don't change are going to be cached on the client by default, anyway, and the browser is intially only going to request the status from the server on subsequent loads...The server should return a 304 not modifed, and the image will be loaded out of the browser's cache.  Regardless,  caching or not won't effect the handling of relative vs. fully-qualifed URLs (the original question) at all.