![]() Regsvr32 "C:\Program Files (x86)\Common Files\microsoft shared\MSEnv\VsLangproj.olb" In NuGet 2.7 or above, when you attempt to install any package which contains assembly references, you may receive the error message "Input string was not in a correct format.", like below: NuGet generated a new NuGet.Config and you should be able to proceed. To fix this: close Visual Studio (on Windows, if applicable), delete the NuGet.Config file, and try the operation again. The NuGet.Config file in your %AppData%\NuGet\ (Windows) or ~/.nuget/ (Mac/Linux) folder has accidentally been emptied. ![]() The result is similar to the image below: In NuGet 3.4 and 3.4.1, when using the NuGet add-in, no sources are reported as available and you are unable to add new sources in the configuration window. Error installing packages with NuGet 3.4, 3.4.1 Store passwords in clear text using the -StorePasswordInClearText option. \nuget.exe sources add -Name Test -Source $Feed -UserName $UserName -Password $PAT When we use the following command to store the credentials, we end up double encrypting the Personal Access Token. ![]() Authentication issues with NuGet feeds in VSTS with nuget.exe v3.4.3 Starting with NuGet 4.0, known issues are a part of the respective release notes. ![]() If you are having trouble installing NuGet or managing packages, please take a look through these known issues and their resolutions. These are the most common known issues with NuGet that are repeatedly reported.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |