Fix for “BIOS Command Limit Reached” error!
Today I opened a web project from a mapped drive (my working directory is on a server that I access via this mapped drive) and had the following error thrown in my face when I tried to run it:
Failed to start monitoring changes to ‘web.config’ 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.
We still run Windows XP at work, and I’ve ran into this problem before (as many other people have), but this time I found a good fix for this issue.
The first half of that blog entry was of no use to me, but the second half was perfect! I chose to set the registry key HKLM\Software\Microsoft\ASP.NET\FCNMode to a value of 2 which causes the application to create one object to monitor the directory and will reuse this same object to monitor all sub-directories.
The fix originally came from Microsoft Support in 911272.




No, I don’t have a problem with Little Bunny Foo Foo. What I’m referring to is a type of coding style where the developer makes a declaration like the following:


