Nuget remote server return error: (403) Disabled

Nuget remote server return error: (403) Disabled

Next, in the previous article, Nuget manages our class libraries. In Step 7, the last package cannot be pushed to the Nuget server. That is to say, even if you use different Nuget API keys for release, no package with the same name is allowed on the Nuget server, that is, the package ID must be different. Although the Nuget tool has been used before, it still takes a lot of time to use it. It is a good way to directly update the tool with a duplicate name, but sometimes it is not the same maintenance, if you want to update an API that requires another user's API Key, you can re-release it by yourself, but you cannot re-name it. However, many of the names in the system are almost the same as those in the previous version. The solution is as follows: modify the class library name. After the Nuget spec command. when editing the ID in the nuspec file, write the name of the changed class library. This indicates that the ID of this package is the package you have just modified, in this way, the package can be pushed to the Nuget server. If you need to change it later, update it directly.

The problem is that you can directly search for the name of the push package when using it. The reference result still does not change the name of the class library. However, when you search for the package name, it is true that you just pushed the package, and the content in the package is also up-to-date. I don't know why the previous class library name is displayed? Guess: a dll file will be generated when the class library is created at the beginning. If you modify it again, there will be some initial residue. You can modify it directly, but you cannot modify the most fundamental thing, after I modify the namespace and assembly, the generated dll name will be changed, but it will not change during reference. If you have any ideas, please contact us.