Ok, I may be going crazy, but I thought I had easily debugged my deployed production version of one of my custom modules before??? It has been a while so I can't remember for sure and after burning a couple hours of googling, I come to you all!

So using Visual Studio 2010 ultimate, can't you debug your remote, deployed, production version of your custom module using the same process (Tools/Attache to Process) just like your local copy? I could've swore I did this...but like I said, I may be a bit off...nights of coding in lieu of sleeping will do that to you.

Anyway, my local code/data debugs fine, but after deployment, I am getting some errors that require me to debug it, hence the question. Is there a way to do this? Note the remote server is on a shared hosting environment.

Thanks in Advance,

Chad