-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Make all nuget packages go in the same folder #1546
Conversation
…a single folder as your nuget repository for testing
Build failed at first, but after running it again seems to have completed. However, no artifacts were generated. |
@nmetulev I updated the appveyor.yml file to look for the artifacts elsewhere, but not sure if appveyor itself needs updating? |
@dotMorten, Up? |
@nmetulev aaah I see. I think the build script does its own thing |
@dotMorten |
@dotMorten, all the nugets right now go to the bin/nupkg folder. is this needed? |
@dotMorten, is this PR necessary. Seems like everything is working right now |
@nmetulev The packages go in the right folder when you use powershell. When you use the right-click->pack in Visual Studio, it goes in the project's output folder. It makes testing specific nuget packages a lot harder, because you have to go and copy them into the same folder so the dependencies can be resolved. |
Ah, I see. I think you probably need to just revert appveyor.yml |
This PR seems inactive. @dotMorten Do you need help to complete this issue? |
1 similar comment
This PR seems inactive. @dotMorten Do you need help to complete this issue? |
@dotMorten, I updated your branch so all nugets go in the existing folder. Would this work? |
This PR seems inactive. @dotMorten Do you need help to complete this issue? |
Makes it easier to use a single folder as your nuget repository for testing, rather than having to dig around all bin folders and combine them manually.
PR Type
Build output folder
What is the current behavior?
Nuget packages are spread out among each project;s sub folders.
PR Checklist
N/A
] Tested code with current supported SDKsN/A
] Docs have been added / updated (for bug fixes / features)N/A
] Sample in sample app has been added / updated (for bug fixes / features)N/A
] Tests for the changes have been added (for bug fixes / features) (if applicable)What is the new behavior?
This change unifies where nuget packages are copied to (
Output\NuGet\Release|Debug\*.nupkg
)Does this PR introduce a breaking change?