XSP Path being generated incorrectly on Windows

Not sure why, but if you choose the Mono .NET 4.0 runtime version in MonoDevelop, the ASP debugger will try and grab the XSP binary from the 4.5 directory, which breaks it since the XSP binary is kept in the .NET 4 lib path on Windows with Mono 3.2.3.

Wasn't sure whether this was Windows specific, though, so it will need to be tested on *NIX to see if it even requires that check, since it seems really counter-intuitive to choose the other folder.