Hi,

   i uploaded my site and when i am doing my project i specified http://localhost/xyzx/123.gif for images and all

    but now when i upload into server it was not showing the images.

i heard that we have to do some changes in web.config or we have to write a program to take the server address insted of local host.

can anybody give a sample program...?

  thanks in advance-Ashok Parchuri

you have to give image file address virtual like if aspx page is on root and images file is in 'images' folder on root then image path should be "images/123.gif". If you give address like this you will not have to change address anywhere you upload site.

You need to pass the physical path of the image to display
it on the page. Server.MapPath gives you the physical path
of the folder in which you have stored the image.

Use:
Server.MapPath("123.gif")

Spacy,

I'm curious why you are recommending the physical address?

Ashok,
When you put a resource URL in a .NET property that expects a resource (such as HyperLink.NavigateUrl or Image.ImageUrl, then you can use the following syntax:

   ~/resourceDir/resource

The ~ character gets replaced with the application root URL. If your web application is called "myapplication" a reference to "~/images/button.gif" will get emitted by ASP.NET like this: "/myapplication/images/button.gif". (This is how it has to work when developing off of a virtual directory of IIS.) If you then move the application to a web host where your website is one of many on the same server then you'll usually reference the site with a root address (www.mywebsite.com). Now the same image URL will get emitted like this: "/images/button.gif".


The second scenario is a little bit harder to deal with. If you have what amounts to hard coded URLs to resources (i.e. they are not set or bound to properties that expect URLs as mentioned above) then you have to be careful how you emit those. There is a method on the Page class called "ResolveURL()" which will do the ~ resolution for you. Then the situation I described earlier will apply and you won't get broken resources.

The important thing is to NEVER use fully qualified URLs unless they are going to "offsite" resources (such as references to production web services or other sites or their resources).

-Peter