Latest on twitter:
So I went to fix a bug in a clients site the other day, loaded up visual studio as usual and went into debug to see if I could find the problem.
However no matter what I did I was getting the error “Unable to start debugging on the web server” Now considering I thought I hadn’t touched anything for some time I was surprised to say the least.
Next I tried to just load the site in the usual manor (as it is a legacy application as a website not a web application). On doing this I just received a blank page, after loading Fiddler to try and get a better look I still got nothing to tell me what was going on but Fiddler said a 500 error was occuring.
Anyway, after uninstalling various pieces of .NET and lots of Google searches. I went to add the logging features of IIS7 to help me out (for some reason they weren’t installed). I can’t remember what exactly but I also had to add some error options on.
Once this was done I was told the actual error message, basically that I didn’t have permission to read the web.config. Simple fix and away we go.
One word to sum up the entire ordeal, ANNOYING.