-
Notifications
You must be signed in to change notification settings - Fork 251
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
Same project reference names have different casings in packages lock file #8581
Comments
Point of clarification, the fact that the case is different in the file isn't really a concern (in my opinion at least). The issue is that restoring without the project changing can cause the lock file to change, just as in #7840. |
@zivkan - i'm unclear with what we should do based on your statement. Is this good or bad behavior in the lock file? Why? |
We should change the
|
Hi @nkolev92 , as @erdembayar and I are checking compatibility issues, may I know if the case change in the lock.json file will cause compatibility issue? Thanks! |
No, this is an old issue. |
Could this result in a NU1004 error? I'm attempting to diagnose why project A by itself restores ok, but when it is referenced by project B, then project A is reported as having changed dependencies. This is in dotnet 5.0.302 |
Afaik, it shouldn't. Would you mind creating an issue that we could have someone validate? |
Details about Problem
NuGet version: NuGet Client Dev\5.4.0.6233
VS Version: Master\29311.58
OS: Windows-10-Enterprise-19H1-04-05-2019
Detailed repro steps
Expected
Same project reference names should have the same casings in lock file.
Actual
Same project reference names have different casings in lock file as below screenshot.
![CasingIssue](https://user-images.githubusercontent.com/20632625/64770080-12885c00-d57f-11e9-8f58-393ddbe5fa72.png)
Note
It started to repro from fixing of the bug 7840.
The text was updated successfully, but these errors were encountered: