-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Update samples to .NET 9 #5882
Update samples to .NET 9 #5882
Conversation
I'll defer #5113 to a follow-up PR since this PR is big enough already - this is ready for review. |
<configuration> | ||
<packageSources> | ||
<clear /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing this will trigger an alert. All NuGet.config files need to have a <clear />
element to avoid implicit feed to nuget.org.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed it because for the purposes of this sample, users probably won't want to use our nuget.org mirror - since it doesn't have all packages and others can be several versions behind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We determined with #5787 that using NuGet.org for the purpose of validating user scenarios is acceptable.
I'm working on getting the manifest.samples.json to work with the build matrix generation now. It's creating some duplicate legs since we've got 8.0 and 9.0 samples now. @mthalman, @richlander, @MichaelSimons, any other feedback on the actual samples content? |
The markdown link check failures are due to #5872 (comment) (not an actual issue with this PR). They would be fixed by dotnet/docker-tools#1446. |
Related
Updates
samples/8.0