Use dotnet-public feed instead of NuGet.org for NuGet packages in Dockerfiles #1290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1286
AI generated summary
This pull request updates how NuGet packages are sourced in Dockerfiles and sample projects, switching downloads from the public NuGet.org feed to the Azure DevOps dotnet-public feed. This improves reliability and consistency for package retrieval, especially for Roslyn compilers and reference assemblies. It also adds explicit NuGet configuration to sample apps and removes a permissive network policy from pipeline configuration.
NuGet package source updates:
microsoft.net.compilers.2.9.0.nupkg,microsoft.net.compilers.3.6.0.nupkg) to use the Azure DevOps dotnet-public feed instead of NuGet.org, across all relevant templates and image definitions.Microsoft.NETFramework.ReferenceAssemblies.*NuGet packages.manifest.versions.jsonto centralize feed configuration.Sample project improvements:
NuGet.configfiles to sample projects (aspnetapp,aspnetmvcapp,dotnetapp) to explicitly point to the dotnet-public feed, and updated Dockerfiles to copy these configs for reliable restores.Pipeline configuration: