| 9:45 pm on Feb 24, 2011 (gmt 0)|
There is a lot to consider here. If they have pages ranked in the search engines or other websites link to them, affiliates, there can be a serious impact (loss of traffic/sales/ etc..)
I would really ask if it needs to be upgraded first. If so, tread lightly. I am sure it is more than just renaming file extensions for the most part. If there is a shopping cart in place, it may need to be replaced.
| 9:56 pm on Feb 24, 2011 (gmt 0)|
The site did need to be upgaded and now has been. We have not yet made it live though. So really the question is what steps do we need to take to minimize the negative impact of the new page names.
| 11:44 pm on Feb 24, 2011 (gmt 0)|
A IIS 7 server can be configured to read .net code from .asp files, no need to use .aspx
| 4:39 pm on Feb 28, 2011 (gmt 0)|
As scooterdude says you can configure IIS to treat .asp page requests as .net - in fact we did this already on s site.
However it can then be a pain for the developer as the usual tools (Visual Studio etc) isn't as helpful if the file extension isn't what it expects.
I'd think about creating .asp 301 redirection pages - I did this with a migration from PHP to ASP a while back and it seemed to work just fine
| 5:14 pm on Feb 28, 2011 (gmt 0)|
Thanks for the info. I think asp redirection pages are the way to go. What is the best way to determine which asp pages are indexed and need the redirection?
| 5:38 pm on Feb 28, 2011 (gmt 0)|
To be honest unless you have a ready made list from analytics etc I'd go with gut feel - home / category / product pages of course should be pretty frequent landing pages both from SERPS and external links.
| 1:49 pm on Apr 22, 2011 (gmt 0)|
Is the redirect the best practice to cover the ASP to .NET issue? Will performance of a site be effected by the mixing of these two language types?