Using Friendly URLs in ASP.NET Web Forms

Introduction

Websites often need to generate SEO friendly URLs. In ASP.NET Web Forms applications, a URL is tied to a physical .aspx file. This default mapping between a URL and physical file makes it difficult for Web Forms applications to generate SEO friendly URLs. One option available to ASP.NET developers is to use URL routing features. Alternatively they can also use Friendly Urls - a feature that allows you to quickly and easily use SEO friendly URLs in Web Forms applications. This article discusses how.

Overview of Friendly URLs

Suppose that you are developing a blog engine that has a web form, say WebForm1.aspx, for displaying a blog post. Traditionally developers passed blog post ID in the querystring of WebForm1.aspx so that different blog posts corresponding to the post ID passed can be displayed. In this arrangement the URLs for different blog posts will look like this:

  1. http://somewebsite/WebForm1.aspx?postid=1
  2. http://somewebsite/WebForm1.aspx?postid=2
  3. http://somewebsite/WebForm1.aspx?postid=3

 

Inside the #1 Cloud Platform for Building Next-Gen Apps
Download Now
 
 

Such URLs are obviously not SEO friendly URLs. Wouldn't it be nice if you could generate friendly URLs in the following format?

 

  1. http://www.somewebsite/WebForm1/2013/03/10/1234

As you can see from the above URL, the WebForm1 is used without any file extension. Additionally, blog post information such as year, month and day of publication is appended to the main URL along with the post ID. This way each blog post gets a unique URL without using any querystring parameters. Such URLs can be easily generated using ASP.NET FriendlyUrls. Moreover, it takes just a few lines of code to generate these URLs.

Installing Friendly Url via NuGet

In order to use ASP.NET FriendlyUrls you need to install the required assemblies using a NuGet package. So, open Visual Studio 2012 and create a blank ASP.NET Web Forms application. Then click on the Project > Manage NuGet Packages menu option. In the resulting dialog search for FriendlyUrls. You should see the Microsoft ASP.NET Friendly URLs entry listed as shown in the following figure.

Microsoft ASP.NET Friendly URLs

Microsoft ASP.NET Friendly URLs

Once you install the necessary NuGet package you will find that a reference is added to the Microsoft.AspNet.FriendlyUrls assembly. Now you are ready to use FriendlyUrls in your application. 

Enabling Friendly Urls

Next, open Global.asax file in Visual Studio and write the following code in its Application_Start event handler.

  1. protected void Application_Start(object sender, EventArgs e)
  2. {
  3. RouteTable.Routes.EnableFriendlyUrls();
  4. }

The above code calls the EnableFriendlyUrls() method on the Routes collection. Calling the EnableFriendlyUrls() method enables FriendlyUrls for your application and you can use all the Web Form URLs without the .aspx extension. For example, instead of accessing a web form as /samplewebsite/WebForm1.aspx you can simply say /samplewebsite/WebForm1

Remember that EnableFriendlyUrls() is an extension method and you must import the following namespaces at the top of Global.asax.

  1. using System.Web.Routing;
  2. using Microsoft.AspNet.FriendlyUrls; 

Getting Information about FriendlyUrls

Inside the Web Form you may want to know the path information about a FriendlyUrl. You can easily obtain that information as shown below:

  1. string path = Request.GetFriendlyUrlFileVirtualPath();
  2. string ext = Request.GetFriendlyUrlFileExtension();
  3. string friendlyurl = FriendlyUrl.Resolve("~/WebForm2.aspx");
  4. string link = FriendlyUrl.Href("~/WebForm1", 2013, 03, 10, 1234);

As you can see from the above code, several extension methods get added to the Request object. The GetFriendlyUrlFileVirtualPath() method returns the virtual path corresponding to the FriendlyUrl being accessed. For example, for a friendly URL http://somewebsite/WebForm1 it will return ~/WebForm1.aspx

The GetFriendlyUrlFileExtension() method returns the physical file extension of a FriendlyUrl. For web form files, it will be .aspx.

You can also generate FriendlyUrls via code using the Resolve() method of the FriendlyUrl class. The Resolve() method accepts a virtual path and resolves that path to the corresponding FriendlyUrl.

The Href() method of the FriendlyUrl class can be used to generate hyperlink URLs. It accepts the virtual path of the FriendlyUrl followed by URL segments (more on that later). For example, if you wish to generate a hyperlink that points to /somewebsite/WebForm1/2013/03/10/1234 then the first parameter will be ~/WebForm1 and URL segments will be 2013, 03,10 and 1234.

Accessing URL Segments in Code

FriendlyUrls features are not limited to generating extensionless URLs. You can also pass data to the underlying Web Form through URL segments. In the blog engine example we discussed earlier, the year, month and day of publication is passed to the Web Form along with the post ID. These pieces of information are passed as URL segments as shown below:

  1. http://www.somewebsite/WebForm1/2013/03/10/1234

The URL segments that you pass along with a FriendlyUrl can be retrieved inside the Web Form code-behind file as shown below:

  1. IList<string> segments = Request.GetFriendlyUrlSegments();
  3. BlogPost post = new BlogPost();
  4. post.Year = int.Parse(segments[0]);
  5. post.Month = int.Parse(segments[1]);
  6. post.Day = int.Parse(segments[2]);
  7. post.PostId = int.Parse(segments[3]);

As you can see, the code-behind uses the GetFriendlyUrlSegments() extension method on the Request object. The GetFriendlyUrlSegments() returns an IList of string. Once retrieved you can access and parse the individual segment and assign to a class named BlogPost. The BlogPost class is a simple class with four public properties, viz. Year, Month, Day and PostId.

  1. public class BlogPost
  2. {
  3. public int Year { get; set; }
  4. public int Month { get; set; }
  5. public int Day { get; set; }
  6. public int PostId { get; set; }
  7. }

FriendlyUrls and ValueProviders

It is also easy to use FriendlyUrls with data bound controls such as GridView and FormView. Consider, for example, that the Web Form that displays a blog post houses a FormView control to do so. The FormView control can use SelectMethod and ItemType properties to specify a method returning the data to be bound and type of the data being returned respectively.

  1. <asp:FormView ID="FormView1" runat="server" ItemType="FriendlyUrlsDemo.BlogPost" SelectMethod="GetBlogPost">
  2. <ItemTemplate>
  3. ...
  4. </ItemTemplate>
  5. </asp:FormView>

As you can, see the ItemType property points to the BlogPost class you created earlier and the SelectMethod property points to a public method named GetBlogPost(). The GetBlogPost() method is shown below:

  1. public BlogPost GetBlogPost([FriendlyUrlSegments(0)]int year,
  2. [FriendlyUrlSegments(1)]int month,
  3. [FriendlyUrlSegments(2)]int day,
  4. [FriendlyUrlSegments(3)]int postid)
  5. {
  6. //you may add some custom processing here
  7. BlogPost post = new BlogPost();
  8. post.Year = year;
  9. post.Month = month;
  10. post.Day = day;
  11. post.PostId = postid;
  12.  
  13. return post;
  14. }

As you can see the GetBlogPost() method has four parameters, viz. year, month, day and postid. These parameter values will be passed through the URL segments as discussed earlier. You need to map the URL segments with the appropriate method parameters. You can do this using the [FriendlyUrlSegments] attribute. The [FriendlyUrlSegments] attribute is a value provider and is applied to various parameters of the GetBlogPost() method. It takes an index of the URL segment you wish to bind with a method parameter. In the above example, if you have URL like this:

  1. http://www.somewebsite/WebForm1/2013/03/10/1234

Then year, month, day and postid parameters will be 2013, 03,10 and 1234 respectively. Although the above example simply constructs a BlogPost object based on the URL segment values you can add any custom processing here.

Summary

FriendlyUrls allow you to generate SEO friendly URLs quickly and easily. In order to use FriendlyUrls you need to add Microsoft ASP.NET FriendlyUrls NuGet package to your project. Once added you can enable extensionless URLs for your Web Forms by enabling the FriendlyUrls feature in the Global.asax. You can also access URL segments and even bind them to method parameters.

 

一个令人蛋疼的 Microsoft.AspNet.FriendlyUrls

 

我一个项目都基本上做完了，结果部署到我服务器的时候结果一直报404 找不到 一看global.asax有个路由注册的代码

1
2
3
4
public static void RegisterRoutes(RouteCollection routes)
      {
          routes.EnableFriendlyUrls();
      }

 放在IIS中 始终是找不到类似伪静态的地址

如：localhost/default这种

找了两天 我还把多个IIS里面的模块都一一比对 还是不对，最后在老外的一篇文章中终于解决了这个问题

http://weblog.west-wind.com/posts/2011/Mar/27/ASPNET-Routing-not-working-on-IIS-70

在web.config 添加

  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true">     
    </modules>
  </system.webServer>

搞定。。。。。。。。。。。。。。。

如果不加上面的话IIS会用自己的解析方式去解析 所以一直解析不到

   记在这里以备后用

posted @ 2016-06-06 12:37  shiningrise  阅读(649)  评论(0)  编辑  收藏  举报
// 侧边栏目录 // https://blog-static.cnblogs.com/files/douzujun/marvin.nav.my1502.css