You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest version, 4.2.1507.118, sets the revision to 4.2.1507.0118 in Moq.nuspec, but has 4.2.1507.118 otherwise, for example in the NuGet feed.
When running Moq with ASP.NET vNext, then dnu restore fails with a "path not found", which expects the missing "0" in the revision number.
If the problem related that the build is rounded to 3 digits for some cases?
In the build file, I see <Revision>$([System.DateTime]::UtcNow.ToString("ddHH"))</Revision>, which translates to the following line in Moq.nuspec: <version>4.2.1507.0118</version>
As a temporary workaround, I am downgrading to version 4.2.1312.1622.
Thank you!
The text was updated successfully, but these errors were encountered:
The latest version, 4.2.1507.118, sets the revision to 4.2.1507.0118 in Moq.nuspec, but has 4.2.1507.118 otherwise, for example in the NuGet feed.
When running Moq with ASP.NET vNext, then
dnu restore
fails with a "path not found", which expects the missing "0" in the revision number.If the problem related that the build is rounded to 3 digits for some cases?
In the build file, I see
<Revision>$([System.DateTime]::UtcNow.ToString("ddHH"))</Revision>
, which translates to the following line in Moq.nuspec:<version>4.2.1507.0118</version>
As a temporary workaround, I am downgrading to version 4.2.1312.1622.
Thank you!
The text was updated successfully, but these errors were encountered: