title: Debugging DotNetNuke Modules
body: <p>What is the best VS solution setup for DotNetNuke 4.8 inter-module communication development?  </p>
  
  <p>I currently have a solution with multiple Web Application projects in it for my DotNetNuke modules - and in each one of those have pages with the controls on them as a test harness.  That all worked fine up until the point where I need the modules to start talking with each other using IModuleCommunicator and IModuleListener - but now that I'm doing inter module communication, debugging won't work out that way anymore.</p>
  
  <p>I'm curious as to how other people handle this - is there a way to have your test pages mock a Nuke environment?  Do you test right in a nuke website?  My solution is in sourcecontrol using VSS, so I don't want to add the full nuke website as a project in my solution since that would force me to add it to source control - and I'd rather not have a full nuke site in source control.</p>
  
  <p>I've been able to debug by attaching to the local IIS worker process, but that's kind of a pain.  Does anyone have any suggestions as to how to ease the pain of debugging inter module communication?  </p>
  
  <p>Any suggestions would be greatly appreciated.</p>