Handling Legacy URLs with ASP.NET MVC(mikesdotnetting.com)

submitted by reperioreperio(405) 2 years, 11 months ago

According to Google's Webmaster tools, there are about 15,000 incoming links to my site. 13,000 of those reference a .ASPX file on disk. When I convert to MVC, with new Search Engine Friendly urls, all those links will break unless I do something about it. Presenting users with a 404 - file not found is not an option. I need to show them the content they were expecting, and update Search Engines with the news that things have changed. Here's how I will be managing those Legacy URLs.

1 comment |category: |Views: 254

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by zigamorphzigamorph(3319) 2 years, 11 months ago 0

Wouldn't it just be better to use a URL Rewriter so you don't have to compile and deploy every time you find a new legacy URL that you need to handle? For example if you used the URL Rewriter at http://urlrewriter.codeplex.com, and created an extension module for it like indicated here http://www.coderjournal.com/2008/12/creating-extension-module-net-url-rewriter-reverse-proxy/ you could accomplish the same thing, with out having to try to integrate old legacy URL's in to your brand spanking new app. :)

Reply

information Login or create an account to comment on this story