Or Why I Really Need to Get Away from ASP Classic
First, a Minor Rant
As a web developer, I deal with hundreds of websites. I’ve got one – exactly ONE, that is still in ASP Classic. And, as the owner of that site, I have no excuses for not rewriting it in PHP – outside of the fact that it’s huge, complicated, and I’m always busy trying to keep my client’s happy.
The Point of this Post
I needed to do some real maintenance on this ASP Classic site. My main development computer is a WAMP server, and is fairly dedicated to my work, so I didn’t want to monkey with setting up IIS there. But my laptop I rarely use, has Windows Vista on it (yikes), and is already running IIS – so I figured it’d be a slam dunk to install SQL Server Express and start working. Alas, I was mistaken.
See my post on Installing SQL Server Express for the headaches on that part of the job. But, once it was finally up and running, I next needed to enable IIS7 to run my ASP Classic code.
Thanks to the wonders of Google, I found out how to enable it quickly. Just go to “Control Panel”->Programs->Turn Windows Features on or off, and within that expand IIS, then World Wide Web Services, then Application Development Features, then just check the boxes for ASP and Server Side Includes, and I was good.
But then, I kept getting 404.3 errors when I would try to view my ASP pages. I tried EVERYTHING I could think of, and it was only after finally finding Ryan Dunn’s article that I was able to get things rolling. Following his directions, through the IIS Manager Remove then Add back your website, and voila – it begins inheriting the proper handler for the ASP code. Thanks, Ryan!