Just wondering if anyone can test this, or if anyone at MS is passing and somehow knows if this is fixed or planned to be fixed.

When you run solutions over network shares you tend to hit a wall after awhile which is due to a limit on network bios commands. I had hoped that Vista didn't have a hard coded limit (which XP SP2 appears to have) but I think I'm wrong about that.

In our situation, we have a Windows 2003 server that acts as our internal 'master' server. It does everything for us- handles our internal DNS tld, runs IIS6, runs file shares.

We also keep all our files on the server and it manages our tape backups for us.

Naturally then we use our developer machines to open solutions from the server. In our case these are web solutions, after you get enough folders in a solution, it becomes literally impossible to build the solution. This I've come to realise is because build time issues folder watchers for each folder within the solution, quickly overloading the network bios command limit.

However, our quick fix was to put the solution on our local machines and redirect our IIS directories on the server to look at our developer machines. Of course- builds started to work again, but we got intermitent runtime errors from the server giving us a similar network bios command limit error.

Of course this is because the situation is now reversed, the server is trying to monitor the folders on our dev machines network shares. And while the errors don't happen enough to cause a problem. It made me realise that web cluster servers surely cannot function in this mannor.. I put it down to Windows 2003 probably not having a network bios command limit (or at least being configurable) and as such- allowing Windows 2003 > Windows 2003 communication to be as rich as possible.

This didn't appear to be the case however- from what I can see- the command limit is still hard coded in 2003. But MS has a fix you can apply for which has some updated dlls and such which aparently tell asp.net to monitor just the root folder of a network share and it will work perfectly fine from this.

Given this fix is available on the runtime side, I wondered- why isn't Visual Studio issued with a fix that makes it issue just a single folder watcher for just the root?

Any plans to fix this? any ways AROUND this? (such as, does visual sourcesafe fix this?)

I've asked similar questions on this before but never had a good response. It also appears that MS has kept very quiet about this problem- despite it becoming very synonymous with asp.net and visual studio 2005 in network share situations.

It really isn't efficient for us to work off our local machines, it makes our entire work solution pointless and makes us inefficient and worse yet- highly susceptible to version problems and data loss.

Thanks,
Stephen.