stevo_ wrote:
Problem is, I can't work locally.. we need the information to be stored on our network for security, and the network contains an internal webserver and dns server, we run our own internal TLD for debugging web solutions, and as such- we need all our solutions to be accessible by the web server.
This means we don't run traditional debugging anyway, such as running the web application and it launching a test development local server, and then starting IE at its location.
Infact- I find it very annoying to debug in such a way. Instead, we simply compile and run the solution as any other person would view the site, catching runtime exceptions that way.
Well, I see no reason why the information has to be on the network for security, usually security is about the data... unless your application code is so secure you cannot keep it locally (: If it isn't, then work on setting up a sandbox environment so you can run it locally and publish your changes out when you're done.
Have you tried remote debugging? Attaching to a remote machine's aspnet process? I assume you have your own custom error information pages if you're doing it manually.... but I can't imagine actually doing everything remote! Ouch!
