Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ResolvePackageDependencies Task does not work on case-sensitive file systems #76

Closed
brthor opened this issue Aug 22, 2016 · 1 comment
Closed

ResolvePackageDependencies Task does not work on case-sensitive file systems #76

brthor opened this issue Aug 22, 2016 · 1 comment

Comments

@brthor
Copy link
Contributor

brthor commented Aug 22, 2016 •
edited
Loading

The issue is that nuget lower-cases all file paths in the nuget cache, and ResolvePackageDependencies should do the same.

https://github.com/dotnet/sdk/blob/master/src/Tasks/Microsoft.DotNet.Core.Build.Tasks/ResolvePackageDependencies.cs#L329
@brthor
Copy link
Contributor Author

brthor commented Aug 22, 2016

@eerhardt @natidea

@brthor brthor mentioned this issue Aug 22, 2016
Closed
@eerhardt eerhardt mentioned this issue Aug 22, 2016
Merged
nguerrera pushed a commit that referenced this issue Oct 10, 2016
@eerhardt
Use the NuGetPackageResolver to get the package directory path instea…
f6c0f3a 
…d of using the environment variables ourselves.

Fix #24
Fix #76
sbomer pushed a commit to sbomer/sdk that referenced this issue Sep 19, 2017
@weshaggard
Make netstandard2.0 API compatible with netstandard1.x (dotnet#76)
622e5b3 
This change adds all the APIs that were supported in netstandard1.x
and were part of the NETStandard.Library 1.6 meta-package closure.

By doing this we are introducing some APIs that aren't going to be
compatible with .NET 4.6.1. If they are used they will throw
MissingType or MissingMethod exceptions. We chose to be back compatible
with netstandard1.x over 100% compatible with .NET 4.6.1. To see the
incompatible APIs refer to ApiCompatBaseline.net461.txt.

To help mitigate people using these APIs we have decided to mark them
with EditorBrowsableState.Never which will hide them in intellisense.
Once the target platforms support these then we will remove those markers
and expose them to intellisense.
@blackdwarf blackdwarf mentioned this issue Jan 31, 2020
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brthor