NuGet remote server returned error:<403> Forbidden

Then in the previous article,NuGet managed our class library at the seventh step when the last package could not be pushed to the NuGet server, that is, even if you publish with a different NuGet API Key can not be, others quoted time will not be able to separate, So a package with the same name is not allowed on the NuGet server, that is, the package ID must be different. NuGet This tool, although has been used before, but this use or spend a lot of time, on a name-name problem, direct update is a good way, but sometimes not the same maintenance, if you want to update also need someone else's API Key, re-publish, you can not duplicate the name, But now many of the system naming is almost the same as the previous version, this time the solution is: the class library name has been modified so that the NuGet spec command, When you edit the ID of the. nuspec file, write the name of the class library after the change, which means that the ID of the package is now the package you have just modified the class library, so that the package can be pushed to the NuGet server, and later need to change the direct update on the OK.

Again, when using the name of the direct search you push the package, the result refers to the name of the class library has not been modified before, but the name of the search package did you just push the package, and the contents of the package is also the latest, do not know why the display is the previous class library name? Guess: The first to build a class library will generate a DLL file, if you modify the words will have some initial residue, you can modify directly on it, but not the most fundamental thing, I changed the namespace and the assembly, the generated DLL name will change, but the reference time will not change. What do you have in mind, welcome to exchange.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

NuGet remote server returned error:<403> Forbidden