views:

1120

answers:

3

We have some basic C# logic that iterates over a directory and returns the folders and files within. When run against a network share (\\server\share\folder) that is inaccessible or invalid, the code seems to 'hang' for about 30 seconds before returning back from the call.

I'd like to end up with a method that will attempt to get folders and files from the given path, but without the timeout period. In other words, to reduce or eliminate the timeout altogether.

I've tried something as simple as validating the existence of the directory ahead of time thinking that an 'unavailable' network drive would quickly return false, but that did not work as expected.

System.IO.Directory.Exists(path) //hangs 

System.IO.DirectoryInfo di = new System.IO.DirectoryInfo(path); //hangs

Any suggestions on what may help me achieve an efficient (and hopefully managed) solution?

+4  A: 

Place it on its own thread, if it doesn't come back in a certain amount of time, move on.

Al Katawazi
+2  A: 

Perhaps you could try pinging the server first, and only ask for the directory info if you get a response?

mquander
I have used this successfully for walking our network of machines, looking for software.However, it may not be feasible to parse out the server from the UNC path.
John Gietzen
+1  A: 

You can see a solution at this site C# How to limit method execution time – Generics implementation