-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Bug] NuGet files not found - possible file length limitation? #66
Comments
As I've been researching it, it seems there is no sure-fire solution if you are using Visual Studio - it's ultimately a problem with Visual Studio. There are workarounds, and some of them work okay. Here's a summary of what I've found. You can...
I'm being somewhat vague here rather than giving exact suggestions because this is covered fairly well in this github issue: Also, the problem seems to be ultimately caused by Visual Studio, and this suggestion is open at the time of this writing. If this affects you then please upvote - maybe it has an impact: https://developercommunity.visualstudio.com/t/Allow-building-running-and-debugging-a/351628 It's worth noting that this specific package is even referenced there: Also it's worth mentioning that there's another firebase library (sorry for mentioning the competition) which calls out this issue as well: https://github.com/TobiasBuchholz/Plugin.Firebase?tab=readme-ov-file#windows-11-long-path-issue Perhaps this info is enough but it's also possible that others may not find this issue yet run into this problem so having it on the main page would be helpful. Feel free to close this issue if you think this comment is sufficient for others who may run into this problem. |
Thanks for your research, much appreciated! I‘ll update the FAQ.md in this repo with your findings. |
I updated the FAQ.md in this repository. Thanks again for your contribution! |
Description
Steps to Reproduce
Expected Behavior
Actual Behavior
I suspect this may be happening because of file length limitations; however, I did specify supporting long file paths in the registry:
And also in the local group policy:
I realize that this is not necessarily a problem with this nuget package; however, this package does result in very long file names, and I'm guessing this may be the problem. Also, I've encountered this problem on multiple machines (mine and my co-workers) which started when we added this library.
If it is truly a windows (or NuGet) configuration problem, perhaps the docs could explain how to avoid this issue?
EDIT 1:
For some reason the errors are inconsistent but they all seem to have to do with nuget files. Here's another set of errors:
Basic Information
Screenshots
N/A
Reproduction Link
The text was updated successfully, but these errors were encountered: