Winton DeShong

Web / Flash Development

Today I experienced quite the issue with my ASP.NET development environment. I have been using a virtualized instance of Windows XP Pro with VMWare/Parallels for quite some time now without any issues. Apparently, none of my previous experiences has quite the same amount of files and directories as my latest project. While developing some ASP.NET 2.0 SOAP web services I began to receive the following error in Visual Studio 2008:

An error occurred loading a configuration file: Failed to start monitoring changes to ‘[…]’ 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.

After the typical procedure of restarting Visual Studio and restarting IIS I was out of luck. I tried to by pass the error being that it really had nothing to do with what I was doing. Finally, after quite a lengthy conversation with Sir. Google, I found a solution. Not the most elegant solution, but a solution nonetheless. Heck, what solution is elegant when developing on Windows? I digress…

Anyway, without wasting any more time that you probably have wasted with this issue, here is the fix.

You need to add an additional registry key:
Add the following DWORD value at the following registry key:

HKLM\Software\Microsoft\ASP.NET\FCNMode

The following table lists possible values for the FCNMode DWORD value and the behavior that is associated with each value.

Value Behavior Does not exist This is the default behavior. For each subdirectory, the application will create an object that will monitor the subdirectory.

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.

Finally, after applying the registry changes, don’t forget to restart your Visual Studio. Good luck!

About two weeks ago, my Macbook Pro starting *squealing* while I was at work. At the time, I was using Adobe Flash CS4 as part of the pre-release of Adobe Design Premium CS4 and began to blame it on the current build. After two to three more occurrences it was just straight up annoying and I looked into the issue. Turns out many people have been having issues with the fans of their Macbook pros, in particular…the right rear fan
.
Well, after monitoring the situation for a few days I decided mine was on it’s way out and ordered a new one. For anyone reading this, don’t simply go purchasing a new fan right away! If you are experiencing issues with a fan in your macbook, I highly recommend running the application smcFanControl. This handy application allows you to not only monitor the RPMs and temperature of your laptop’s individual fans, it allows you to individually adjust the RPMs.

If you keep tabs on the RPM rate of your fans with this tool you should be able to prevent any issues before they happen.