-
Notifications
You must be signed in to change notification settings - Fork 258
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
Provide samples for coding against NuGet 3 codebase #2243
Comments
Thanks! Original request was #1870 |
This will be a massive help, thank you. |
any update on this? |
Last info I've seen is a comment on this blog post which stated
|
FWIW, I've got a blog series looking at the v3 APIs, though it's all based on spelunking through the code so I may have gotten some aspects wrong:
|
@daveaglick nice will definitely check those out 👍 |
@devlead That's the reply to my comment! I've emailed them asking for anything they have, even referencing this issue, just waiting for a response now.. |
@agc93 ok cool 👍 Please ping back if you get any solid info, |
I got a reply back from the team basically outlining that they don't have much information and actually indicating that Dave's blog posts are their best source currently! Full response below:
|
Any progress on this one. The API is not very well documented and using it involves lots of guessing with regards to how to do things. |
@ferventcoder did you find the replacement of ZipPackage in NuGet.Client? |
Need to enumerate common scenarios we want to show as samples, going to take a quick stab and will keep refining as feedback comes in
Would be nice to contrast samples from nuget.core with the NuGet3 codebase.
We will gladly take pull requests to https://github.com/NuGet/docs.microsoft.com-nuget as folks find good ways to port over, and of course sample projects to https://github.com/nuget/samples utilizing the new API. I'm also open to running a CI on top of the samples to ensure breaking changes are at least known, if not immediately addressed.
The text was updated successfully, but these errors were encountered: