-
Notifications
You must be signed in to change notification settings - Fork 99
InvalidOperationException on Directory.EnumerateFileSystemEntries() #441
Comments
curious.. how about other unc/local paths? |
Ok . How can i see the "next folder or file returned" ? NAS logs or PC logs? |
Hm.. the only way I can think of is using the VS debugger. |
Hi Yomodo. |
Hi Yomodo. Was this iTrace file useful to you? Do you need more information? |
Hi CyberSinh, thanks for this. Will analyze this in the next days. |
Unfortunately, I only have access to VS 2015 Enterprise, loading the .Itrace throws a waring that I'm not able to view all the information. However, the Exception is thrown here:
If you can place a breakpoint and run debug again, you should be able to see exactly what data win32FindData and regularPath contain. Hopefully this can tell us more. |
I think the fix is simple; could you change this line:
to: if (null != handle && lastError != Win32Errors.NO_ERROR)
|
Thank you very much Yomodo! |
It works? Cool! |
I will propose a modified version of AlphaFS to the user concerned by this issue to check if the patch works. I'll keep you informed. |
I'm sorry but the user concerned has told me that the patch does not work. The same error always occurs. Here is the new IntelliTrace log: |
I've made a new branch #441 based on the latest master. Could you test again with this? |
Everything works fine with this new branch. You can merge it. Thank you. |
Any timinig for a new maintenance nuget release? |
Soon, I'll start preparing. |
Hi,
If I run these commands under PowerShell:
I get the following output:
As you can see, the target folder is well identified as a directory by AlphaFS. However, if I try to enumerate the contents of this folder, I get an error "the target directrory is a file, not a directory".
Does anybody know why?
Thanks.
The text was updated successfully, but these errors were encountered: