Someone off the topic, in moving from ADOGuy.com to Wildermuth.com I used IIS's trick of a permanent redirection to point old links to the new site and this seemed to work...kinda...sorta.
Very old links to ADOGuy.com (before I used blog URL's that were friendlier) took the form of "/Content.aspx?id=rantview&rantid=317" which I had code to redirect automatically to the right rant. But...
The IIS redirection was truncating the query string. I googled my head off and was begging people on Twitter for a non-code fix (I could have written a handler, but I was hoping IIS could do it for me). That';s when I ran into this great post that fixed it for me!
The trick (which you can read on DeveloperFusion's blog entry) is to check "A permanent redirection for this resoruce", click "The exact URL entered above" and add a $S$Q to the end of the URL so that the subdirectory and query string are appended as shown below in IIS 6:
Cool, huh? Too bad its not documented better.
I am working in a Window Communication Foundation (WCF) project and I am trying to prototype using SSL for my service calls. I am also working on Vista so I wanted to try out the new Client Signed Certificate feature in IIS7 that Scott Guthrie blogged about a bit ago. I followed the instructions on his blog to the letter with no result.
The error I got when trying to start my site was "The process cannot access the file because it is being used by another process." The file was actually the 443 socket, not a file so this error led me astray for a bit until I found this interesting knowledge base article from Microsoft. It essentially walked me to through finding out who was listening on 443...it turned out to be Skype. Whooa... Killing Skype allowed me to start my SSL site locally. I think I'll just use an alternate port number for now to get around the problem, but at least I know what is happening now.
Whew...
