asp.net mvc using HREF in application running on IIS

Question

There is a partial view representing pager control (very similar to this) for blog content. Code generates HTML with references and href like, "/Blog/Posts/Page/1", "/Blog/Posts/Page/2" etc.

It worked absolutely fine on Cassini, but after I switched to IIS problems appeared.

IIS application running in virtual folder, so URL is

http://localhost/tracky

and blog area located,

http://localhost/tracky/blog

As I press on pager button, I recieve 404, because the URL would be

http://localhost/blog/page/3

Instead of

http://localhost/tracky/blog/page/3

My question is, how to handle such situation? how to change code generation to provide correct URL? how to make it work same - as root applicaton or application in virtual folder?

Source code is here

how are you generating the url?

marcind
– marcind

2010-10-30 21:30:47 +00:00
Commented Oct 30, 2010 at 21:30 — marcind
– marcind, Commented Oct 30, 2010 at 21:30
now it is just hardcoded as "/Blog/Posts/Page" + pageIndex;

Alexander Beletsky
– Alexander Beletsky

2010-10-30 21:42:32 +00:00
Commented Oct 30, 2010 at 21:42 — Alexander Beletsky
– Alexander Beletsky, Commented Oct 30, 2010 at 21:42

spender · Accepted Answer · 2010-10-30 21:34:03Z

3

You need to generate your urls either by using ActionLink in your view, or using an UrlHelper in your href as follows: <a href="<%=Url.Content("~/blog/page/3")%>" ..>bla</a>. This will generate Urls that are adjusted accoring to your application root.

answered Oct 30, 2010 at 21:34

spender

121k36 gold badges245 silver badges369 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Alexander Beletsky Over a year ago

how is it possible to use it from code-behind, HtmlExtension helper class ? I could not find Url namespace

Alexander Beletsky Over a year ago

ActionLink variant works for me... <%: Html.Pager(Url.Action("Page", "Posts", new { area = "Blog", id="{0}"}), Model.TotalPages, Model.CurrentPage)%>

marcind · Accepted Answer · 2010-10-30 21:34:26Z

0

You should be using the following:

UrlHelper.GenerateContentUrl("~/Blog/Posts/Page/1");

The ~ allows the url to be resolved relative to the application path and should produce correct results in both cassini and IIS.

answered Oct 30, 2010 at 21:34

marcind

53.2k13 gold badges129 silver badges112 bronze badges

2 Comments

spender Over a year ago

I think Content instead of GenerateContentUrl will suffice. There's no need to fully qualify the urls.

Alexander Beletsky Over a year ago

UrlHelper.GenerateContentUrl also recieves httpContext, that make it difficult to use code in helper classes.. and unit test it.

Collectives™ on Stack Overflow

asp.net mvc using HREF in application running on IIS

2 Answers 2

2 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related