I'm using ASP.NET and the masterpage architecture on my asp.net portal and when I add a logo to the master page, despite every other page using that same one masterpage, only the homepage will pick up the logo in the masterpage.

So if I add a logo on my masterpage, only the homepage (default.aspx) which is based off site.master will show the logo. Any other page won't. This is despite updating the files on the server (logo, masterpage, etc).

Why is this? I know this isn't really a pre-sales question but this seems to be the best place to ask. Is this a hosting issue?

A few thoughts:

1.  Are the pages that won't show the image in a different folder than default.aspx?  If so, it's a mapping problem.

2.  Do the pages that don't show the logo have the MasterPageFile="site.master" in the Page declaration at the very top?  If not, add it so it uses the site.master.

Also, if your masterpage is in the root of the application but your aspx page isn't (similar to #1 above), make sure you reference the virtual path to the masterpage like so:

The easiest thing to do here is to make sure that you are using a WebConrol for the image (like System.Web.UI.WebControls.Image") and set the ImageURL property to one that is rooted to the application.

 An example would be if the image is in /images/myimage.gif, you would specify the url as "~/images/myimage.gif".  It will automatically translate the tilde (~) into the root of the application.  This way the path will always be correct no matter what the folder hierarchy of the page is.

If you cannot use a WebControl, there is a method defined on Control (and subsequently any Usercontrols or Pages) called "ResolveURL".  You wold pass this the ~ rooted URL and you would get back the correct url.  An example of using this in code would be:

<img src='<%= this.ResolveURL("~/images/myimage.gif") %' />

Hope this helps.