bencoffman.com/blog - MSBuild http://bencoffman.com/blog/ News about Tech and a few other things. en-us Ben Coffman Wed, 01 Dec 2010 21:01:04 GMT newtelligence dasBlog 2.1.8102.813 coffmanben@gmail.com coffmanben@gmail.com http://bencoffman.com/blog/Trackback.aspx?guid=8f7dd337-4433-4dbc-951a-8c77cb5b6641 http://bencoffman.com/blog/pingback.aspx http://bencoffman.com/blog/PermaLink,guid,8f7dd337-4433-4dbc-951a-8c77cb5b6641.aspx Ben Coffman http://bencoffman.com/blog/CommentView,guid,8f7dd337-4433-4dbc-951a-8c77cb5b6641.aspx http://bencoffman.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=8f7dd337-4433-4dbc-951a-8c77cb5b6641


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.
Error 43 An error occurred loading a configuration file: Failed to start monitoring changes to... http://bencoffman.com/blog/PermaLink,guid,8f7dd337-4433-4dbc-951a-8c77cb5b6641.aspx http://bencoffman.com/blog/2010/12/01/Error43AnErrorOccurredLoadingAConfigurationFileFailedToStartMonitoringChangesTo.aspx Wed, 01 Dec 2010 21:01:04 GMT <img src="http://bencoffman.com/blog/content/binary/microsoft_.net_logo.png" width="120px" border="0" height="75px"> <br> <b> <br> <br> Problem:</b> <br> 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<br> <br> <b>Solution:<br> </b> <b>REMEMBER YOU ONLY NEED TO MAKE THESE CHANGES ON YOUR MACHINE NOT THE MACHINE YOU ARE TYRING TO ACCESS</b> <ol> <li> Add the following DWORD value at the following registry key:<br> HKEY_LOCAL_MACHINE\Software\Microsoft\ASP.NET\FCNMode <br> The following list possible values for the FCNMode DWORD value and the behavior that is associated with each value.</li> <li> 0 or greater than 2 - This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.<br> 1 - The application will disable File Change Notifications (FCNs).<br> 2 - The application will create one object to monitor the main directory. The application will use this object to monitor each subdirectory. <br> 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. </li> </ol> <b> DON'T FORGET:</b> <i>If you are running a 64bit version of windows you will need to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET</i> <br> <br> <b>Explanation:</b> <br> 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.<br> <br> This blog (<a href="http://tonybellomo.com/FullBlog.aspx?BlogID=10176">http://tonybellomo.com/FullBlog.aspx?BlogID=10176</a>) helped lead me to my answer, though the 64 bit part through me for a spin.<br> <img width="0" height="0" src="http://bencoffman.com/blog/aggbug.ashx?id=8f7dd337-4433-4dbc-951a-8c77cb5b6641" /> http://bencoffman.com/blog/CommentView,guid,8f7dd337-4433-4dbc-951a-8c77cb5b6641.aspx .Net ccnet MSBuild http://bencoffman.com/blog/Trackback.aspx?guid=05cebcbd-687a-4d7f-af7a-df328e4beb03 http://bencoffman.com/blog/pingback.aspx http://bencoffman.com/blog/PermaLink,guid,05cebcbd-687a-4d7f-af7a-df328e4beb03.aspx Ben Coffman http://bencoffman.com/blog/CommentView,guid,05cebcbd-687a-4d7f-af7a-df328e4beb03.aspx http://bencoffman.com/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=05cebcbd-687a-4d7f-af7a-df328e4beb03


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.



ASPNETCOMPILER : error ASPRUNTIME: Request failed. http://bencoffman.com/blog/PermaLink,guid,05cebcbd-687a-4d7f-af7a-df328e4beb03.aspx http://bencoffman.com/blog/2010/12/01/ASPNETCOMPILERErrorASPRUNTIMERequestFailed.aspx Wed, 01 Dec 2010 19:27:29 GMT <img src="http://bencoffman.com/blog/content/binary/microsoft_.net_logo.png" width="120px" border="0" height="75px"> <br> <br> <br> <b>Problem:<br> </b>Done executing task "AspNetCompiler" -- FAILED.<br> Done executing task "CallTarget" -- FAILED.<br> (default target) (1) -&gt; (Website target) -&gt; ASPNETCOMPILER : error ASPRUNTIME: Request failed.<br> <br> <b>Solution:<br> </b> <p> 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, <a href="http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC&amp;displaylang=en">.NET Framework 2.0 Software Development Kit</a>. Once this kit was installed and downloaded I ran an application called, .NET Framework 2.0 Configuration. In this tool I selected </p> <ul> <li> Runtime Security Policy &lt;-- Once selected in the right pane I selected<ul> <li> "Adjust Zone Security"<ul> <li> Once this is selected I choose</li> <li> "Make changes to this computer." Click Next<ul> <li> On the next screen click "Local Intranet" and move the trust arrow up to "Full Trust" I did it for Trusted Sites also.</li> </ul> </li> </ul> </li> </ul> </li> </ul> <b>Explanation:<br> </b>Remember .Net doesn't let you run assemblies from any which location. Why would they<font size="4"><span class="Unicode"><b>‽</b></span></font> 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.<br> <br> <br> <br> <p> </p> <img width="0" height="0" src="http://bencoffman.com/blog/aggbug.ashx?id=05cebcbd-687a-4d7f-af7a-df328e4beb03" /> http://bencoffman.com/blog/CommentView,guid,05cebcbd-687a-4d7f-af7a-df328e4beb03.aspx .Net ccnet MSBuild Visual Studio