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.
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.
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?
![The Complete Web Development Roadmap [2024]](/img/n.gif)
Just brilliant, thank you very much :-)
Just when I was a little confused about CPM & a video from Steve on the same topic made me happy ❤
Woohoo!
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.
Awesome content as usual
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?
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.
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?
I think just SDK style "new" projects.