Problem:
Error 43 An error occurred loading a configuration file: Failed to start monitoring changes to '[my path]' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform. [my path]\web.config

Solution:
REMEMBER YOU ONLY NEED TO MAKE THESE CHANGES ON YOUR MACHINE NOT THE MACHINE YOU ARE TYRING TO ACCESS

1. Add the following DWORD value at the following registry key:
   HKEY_LOCAL_MACHINE\Software\Microsoft\ASP.NET\FCNMode
   The following list possible values for the FCNMode DWORD value and the behavior that is associated with each value.
2. 0 or greater than 2 - This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.
   1 - The application will disable File Change Notifications (FCNs).
   2 - The application will create one object to monitor the main directory. The application will use this object to monitor each subdirectory.
   I recommend setting the value to 1, to disable the FCN. This is what is causing the error when you try to use the debugger.  

  DON'T FORGET: If you are running a 64bit version of windows you will need to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET

Explanation:
When building over a network I believe MSBuild creates a thread of some sort for each file it's compiling. This tells it to create only one for the entire project/solution. For some reason this fixes it. Ugg these last few posts have been some tuff ones.
 
This blog (http://tonybellomo.com/FullBlog.aspx?BlogID=10176) helped lead me to my answer, though the 64 bit part through me for a spin.

Problem:
Done executing task "AspNetCompiler" -- FAILED.
Done executing task "CallTarget" -- FAILED.
(default target) (1) -> (Website target) -> ASPNETCOMPILER : error ASPRUNTIME: Request failed.

Solution:

What was going on and not being said was the computer I was on didn't trust the assemblies I was using on another computer....We all could have got that from the error right? Anyways, there is a fun little tool called, .NET Framework 2.0 Software Development Kit. Once this kit was installed and downloaded I ran an application called, .NET Framework 2.0 Configuration. In this tool I selected

• Runtime Security Policy <-- Once selected in the right pane I selected
  • "Adjust Zone Security"
    • Once this is selected I choose
    • "Make changes to this computer." Click Next
      • On the next screen click "Local Intranet" and move the trust arrow up to "Full Trust" I did it for Trusted Sites also.

Explanation:
Remember .Net doesn't let you run assemblies from any which location. Why would they‽ That could be a nightmare of security issues, so developers when working on assemblies across the network and things go south always think perms, down to an assembly level.