Secure your NuGet packages with Package Source Mapping

preview_player
Показать описание
Always know where your NuGet packages come from by centrally mapping them to target sources. If you use multiple package sources for your projects, this is a must watch! Christopher Gill demos how to map your packages to reinforce your supply chain security and build reproducibility when using multiple package sources.

#DotNet #nuget #dotnetconf2021
Рекомендации по теме
Комментарии
Автор

I find it rather annoying, since I have mostly fetched from nuget anyway, I now have to reconfigure everything for all projects, which sucks.

DJoneone
Автор

This is a nightmare, every tiny app that uses a packages ask for this "feature" so its dependencies and dependencies of dependencies....
How can this be disabled?!

kronozord
Автор

Can this (Package Source Mapping) be optional?

gordsh
Автор

Hello, where can I found the nuget.config file in my .sln or in my project folder ? I see him nowhere

jaja-rp
Автор

your voice energy was good but I didn't understand even one word of your explanation! (except the part that you said: when we put * it'll install the subcategories that match the longest form of it.)

ghaznavipc
Автор

This is out of date and needs to be updated or removed. VS2022 does not support this

RedDog