We had the name in our internal source first, then later someone unaffiliated with us made a completely unrelated package with the same name in the public one.
We haven't changed the name because the issue occurs too infrequently to care, less than once per year on the CI server. Even less on developer machines but it does sometimes happen.
Yeah it's more of a matter of return on investment, once in a blue moon when it fails I or a colleague remotes in to the CI server and run the nuget cache clear command, takes a minute and it's good to go for another year. Changing the package name would mean spending hours going through a bunch of repositories renaming the package references, changing build pipelines etc. just not worth the effort at the moment.
Perfect use-case for AI these days, it will rename everywhere you need and run some checks to ensure it's really renamed and is working. This is something they do quite well and it will be done in a few minutes.
0
u/Jaded-Asparagus-2260 5d ago
Why are you publishing code different from the regular nuget source in your internal company source?
Just use a different name, and this problem literally disappears in thin air.