Hi J,

good to hear that it works now! But is there a reason why you didn't store the image files in the skin directory? Do you need them for more than one DNN portal? You said the images are in a directory "outside of the DNN structure", but as you describe it further, it's in the root of the DNN directory, that is the directory where the DNN web.config file is in. Am I right?

Anyway, it's not necessary to write the absolute URL in the image path, e. g. <img src="www.domain.com/pngs/hdr-int-1.jpg" />, in fact this will cause you unneccessary work if you want to use the skin on two different servers, e. g. on a development server and a live server. You have two options to make the image path server independent:

• If you need the header images for this specific portal only:
  Move the image directory (I think you called it pngs) into your skin directory (where your .ascx file is in) and access the images in the table of your .ascx file as follows:
  <img src="<%= SkinPath %>pngs/hdr-int-1.jpg" />
  <%= SkinPath %> is a DNN specific tag that DNN will replace with the current skin path (e. g. www.domain.com/Portals/0/Skins/MyDNN-Gray-variation/) at runtime.
• If you really need the images in more than one portal, there is another way to make the image paths server independent:
  Leave the image directory where it is (if it's in the DNN root directory as I suppose) and access the images as follows:
  <img src="~/pngs/hdr-int-1.jpg" runat="server" />
  The ~ (tilda) is an ASP.NET specific character. ASP.NET (not DNN) will replace it with the applications'  current root directory at runtime, if you add the runat="server" attribute as well.