Skip to content

Fixed path too long problem. #552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 3, 2015
Merged

Fixed path too long problem. #552

merged 1 commit into from
Aug 3, 2015

Conversation

baltie
Copy link

@baltie baltie commented Aug 3, 2015

In solutions containing a node_modules folder somewhere, there was a very good chance that you would get a PathTooLongException in DirectoryDateFinder.GetLastDirectoryWrite() since the fully qualified name in one of its sub directories would likely be larger than 260 chars. This change determines last write time in a way that doesn't throw this exception.

It was not possible to create a failing unit test without calling CreateDirectoryW in Windows API directly since .NET refuses to create directories with full path names longer than 260 characters.

In solutions containing a node_modules folder somewhere, there was a very
good chance that you would get a PathTooLongException since the fully
qualified name was larger than 260 chars. This change determines last
write time in a way that doesn't throw this exception.
JakeGinnivan added a commit that referenced this pull request Aug 3, 2015
Fixed path too long problem.
@JakeGinnivan JakeGinnivan merged commit d8dc1ab into GitTools:master Aug 3, 2015
@JakeGinnivan
Copy link
Contributor

Nice change, thanks!

@baltie baltie deleted the path-too-long branch August 4, 2015 07:36
@baltie
Copy link
Author

baltie commented Aug 4, 2015

Thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants