Automatically Convert to Central Package Management

Automatically Use Central Package Management
Hey everyone, I'm Steve Smith aka ardalis, of NimblePros!
In this short video I'm going to briefly introduce central package management, show you how to migrate to using it manually, and then save you a bunch of tedious effort by showing you a tool that will do it automatically. Check it out!
Links
github.com/nim...
devblogs.micro...
learn.microsof...
github.com/Van...
Check out my courses:
academy.nimble... (use code EARLYACCESS for 60% off Identity Essentials)
dometrain.com/...
dometrain.com/...
dometrain.com/...
ardalis.com/tr...
www.pluralsigh...
Team Consulting and Training: NimblePros.com and @nimblepros
Developer Group Mentoring: devBetter.com
Free Weekly Email Tips:
ardalis.com/tips/
If you read this far, I hope you liked this video and will consider subscribing to my channel! Or if you already subscribe, how about adding @NimblePros ?
Find me:
ardalis.com
/ ardalis
github.com/ard...
/ stevenandrewsmith
bsky.app/profi...
#ardalis #stevesmith #dotnet #csharp #programming #nimblepros #visualstudio #cli #nuget #packagemanagement
Keep Improving!

[@marna_li]

Thanks for the tip. I needed that tool!

[@Ardalis]

Happy to help!

[@MdKinawy]

Awesome content as usual

[@Ardalis]

Glad you enjoyed it!

[@afouadr]

Just brilliant, thank you very much :-)

[@Ardalis]

Glad to help!

[@DerekPriceRocks]

i think where it gets tricky is having multiple nuget package sources. We have ours split into third-party and our own. When I played around with this before, I remember this caused quite a bit of friction against adopting this. Maybe things have changed since then.

[@Ardalis]

Yes, I suppose that could be an issue. I have multiple package sources and source mapping and it's worked for me so far, but I can imagine there could be package resolution issues.

[@marktownsend9273]

Just tried the tool, and I have to say, it took a working project and made a pigs ear of it. All of the versions were removed from the csproj, but only half the packages listed in the directory file. Build failed, and worse, I could not open VS Package Manager window because of null errors. To resolve it, had to search one by one through all the project files, find the missing version references, check what was the correct version manually, and add them. In the end, I just rolled back to a previous version. I like the idea of the central versioning, but not sure the tool is battle ready yet.

[@Ardalis]

Really? I've used it on at least a dozen solutions and never had a problem. I certainly recommend doing this in a fresh source control state so that you can easily do a 'git reset' if needed (as in your case) but you're literally the first person I've heard have an issue. I did also hear last week that the .NET Upgrade Assistant is releasing support for central package management now, too, so you might give that a try.

[@pilotboba]

I knew about this. I didn't think it was supported with .Net Framework. But, seems like it might be as long as you have the up to date tooling. Do you know if that tool supports the old style projects, or just SDK projects?

[@Ardalis]

I think just SDK style "new" projects.

[@larsp5109]

How does this work in this scenario: I have a large solution with all kinds of handy projects some of which I use in various solutions I’m working on?

[@Ardalis]

If you want them to use consistent package versions, it should work well.