>By coincidence I battled something similar for an hour today. Spend ages trying to work out whether an image was being cached on the server or on the client.
>Cleared the history on the browser, stopped and restarted both the site and the app pool - still getting the wrong image. Turned out that it was neither of the above - VS hadn't actually updated the image in one of the distribution folders so it wasn't being pushed to the production server.
>
>That said, it probably is not applicable in your case :-{

Those are some difficult ones to troubleshoot. :)