Nuget Error Xxx Is Not A Valid Version String Debug To We checked system environment variables and found that one of the variable was 'version' which was set to latest. removing this variable (eg, unset version) resolved the issue for us. However, when attempting to compile a project, i encountered the following error: c:\program files\dotnet\sdk\ 7.0.403 \nuget.targets: error: 'xwp 10112022' is not a valid version string. why is this causing an issue with nuget, and any thoughts on how to resolve it?.
Nuget Error Xxx Is Not A Valid Version String Debug To The version string given to nuget pack operation is not a valid string. please ensure that the version string passed to nuget pack operation is a valid semver2 string. was this page helpful?. In my case, i was getting the error during "dotnet restore" in my ci pipeline. seems it was due to having a declared variable named "version" in the yaml of the pipeline. When i attempt to view packages for my solution the ui just says "error occurred" with the details below, '' is not a valid version string. my build environment is heavily customized with custom targets, and packages are loaded via an out of vs process called "corext.". Decrease the likelihood of having no letters in the commit hash, by using the full 40 character commit hash ci commit sha instead of the shortened one. this reduces the probability of an invalid version to about 4 * 10 10 or about 1 in 2 billion. make your pre release identifier non numeric.
Nuget Error Xxx Is Not A Valid Version String Debug To When i attempt to view packages for my solution the ui just says "error occurred" with the details below, '' is not a valid version string. my build environment is heavily customized with custom targets, and packages are loaded via an out of vs process called "corext.". Decrease the likelihood of having no letters in the commit hash, by using the full 40 character commit hash ci commit sha instead of the shortened one. this reduces the probability of an invalid version to about 4 * 10 10 or about 1 in 2 billion. make your pre release identifier non numeric. This likely comes from a package reference or a dependency listed as version=“latest” in your *.csproj or packages.config, or even as a package source in your nuget.config. nuget does not recognize “latest” as a valid version; you should specify an explicit version number. After debugging and browsing and getting frustrated, i stumbled upon the issue: running git rev parse short head gave 0125124 which was a number. it is usually a combination of letters and digits, but this time it "appeared" as a number which nuget doesn't like!. In order to fix this i went and found the latest version number from the nuget gallery page for the package and updated the command to include a specific package number instead of the * *:.
Comments are closed.