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

Take out workarounds which mark files from NuGet packages as executable once NuGet starts doing this #946

Closed
dsplaisted opened this issue Mar 6, 2017 · 0 comments
Closed

Take out workarounds which mark files from NuGet packages as executable once NuGet starts doing this #946

dsplaisted opened this issue Mar 6, 2017 · 0 comments
Assignees
@johnbeisner
Milestone
2.1.3xx

Comments

@dsplaisted
Copy link
Member

In #935, I've had to work around NuGet/Home#4424 by explicitly setting files that come from NuGet packages to executable. Once the NuGet issue is resolved, we should remove these workarounds.

Places to be changed:
@dsplaisted dsplaisted added this to the 2.0 milestone May 16, 2017
@livarcocc livarcocc modified the milestones: 2.0.0, 2.1.0 May 27, 2017
johnbeisner pushed a commit to johnbeisner/sdk that referenced this issue Oct 19, 2017
https://github.com/dotnet/sdk/issues/946
e7f8939
@johnbeisner johnbeisner mentioned this issue Oct 19, 2017
Merged
johnbeisner added a commit that referenced this issue Oct 20, 2017
@johnbeisner
#946 (#1670)
5d4aa5c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@johnbeisner johnbeisner

Labels
None yet
Projects
None yet
Milestone
2.1.3xx
Development

No branches or pull requests
3 participants
@dsplaisted @livarcocc @johnbeisner