I have a page that points to a masterpage, which has some links and images on it.

I am doing url rewriting using an httpModule.  So the address www.mysite.com/products would get rewritten under the covers to www.mysite.com/ps/main/products.aspx

 The rewriting is working fine, but when www.mysite.com/ps/main/products.aspx is loaded, it does not seem to properly load the references within the masterpage, such as .css and image files.

Any ideas?

on your page where ever you use images and other css...class...u need to make them runat server and give root path which start with "~/" ...

b'coz when ur url is change then when ever there is local path...then use ur rewirete url as root url and because of that path of those images are not found...

so make all images runat server and give path with "~/" same u can do in CSS...

parth_192 is exactly right!  But this does not apply just for master pages.  I would use it for all of your pages where folders and levels could be an issue.  Visual Studio when selecting links by default will populate with the FQ Link starting with ~/Folder1/Folder2/File.aspx

Good Luck

Brent

Hi,

When You r using URL rewriting u have to be very careful for links and images and other paths

if ur using following type of path 

<img alt="" height="7" src="/Images/logo_bottombar.jpg" width="665" />

then place the

 <%=Request.ApplicationPath%>  before it so now your code will be

<img alt="" height="7" src="<%=Request.ApplicationPath%>/Images/logo_bottombar.jpg" width="665" />

U can do it for CSS also.

It can be helpful to u

Sure if you are using plain HTML controls.  I would suggest that you use the ASP.NET image control for images where the file path could get confused.  It you are having problems with CSS I recommend simply using Themes and throwing the CSS file in a theme folder.  ASP.NET will keep up with the CSS from there on.

Just declare all you css files in Master page and make then runat = "server" which is available for CSS files...so that will not create proble,.. 

Thank you for your quick reply.

I was hoping for a quick fix as you suggested.  Unfortunately, neither css nor images worked.  Here is the part that did not make sense:

This did not work:

<link rel="Stylesheet" type="text/css" runat="server" href="<%=Request.ApplicationPath %>/Main.css" />

But this worked (here ApplicationPath is hard-coded as "/PS"):

<link rel="Stylesheet" type="text/css" runat="server" href="/PS/Main.css" />

Any ideas?

Thank you for your quick reply.

Please see my reply to rikishipabst above, as this situation is identical.

you can write this :

<link rel="Stylesheet" type="text/css" runat="server" href="~/(path from root to main.css file )"/>

Thank you for your quick reply.

Main.css is at the root folder, same as the masterpage.  So href="~/main.css" should work, but does not. Again, hardcoding the AppPath like this- href="/Ps/main.css" makes this work, but of course I do not wish to hard-code the application path.

Any ideas would be appreciated.

Saavik,

I used:

<link id="Link1" rel="Stylesheet" type="text/css" runat="server" href="~/main.css" />

and it worked just fine.  When you load the page View the Source in the browser.  If indeed ASP.NET is loading the StyleSheet location then the problem may not be with ASP.NET but rather when in the Execution Cycle it is populating the href portion of the tag.

 It could also be your lack of giving the Tag an ID.  You tell the code to runat the server but without an ID specified the server cannot render the tag correctly.

Let me know what you get!

Brent

Thanks for your idea.

I added id that was not there before, and still not working.  In fact, the generated source says:

href="../main.css" - this was a real surprise.

Masterpage resides in the root folder, as does main.css.  Masterpage refers to main.css.

The actual page that is built over the masterpage resides in a folder one level down (i.e., ~/Main/Mypage.apsx).

I feel clueless - any ideas?