-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xunit.runner.visualstudio 2.1.0 result in 2.1 in the package folder name when restoring #1708
Comments
|
Are you using latest paket.exe?
|
|
Yes. I'm using the latest stable version (download by paket.bootstrap.exe) |
|
I can't reproduce yet. Can you please create a zip which reproduces the situation just before the second paket install breaks it for you? I will then take a look and try to fix asap. |
|
You can see step by step here: Env: Windows 10, VS2013, VS2015 I run At the third commit, if I delete packages folder and call Note that I pinned version 2.1.0 just in case xunit has any upgrade. In my project I don't pin the version, the result is the same. |
|
OK thanks. I fixed that and paket will not remove the trailing zero in the lock file when version_in_path is true. In order to fix your project:
|
|
Thank you very much for your quick fix. |
I use this in my paket:
nuget xunit.runner.visualstudio version_in_path: trueThe first
paket install, it results inxunit.runner.visualstudio.2.1.0inpackagesfolder and the .csproj refers to this folder.The
paket restore, it results inxunit.runner.visualstudio.2.1inpackagesfolder and it breaks the references in .csproj.The second
paket install, it tried to update the reference toxunit.runner.visualsudio.2.1, which is an inconsistant behavior with the first install.The text was updated successfully, but these errors were encountered: