-
Notifications
You must be signed in to change notification settings - Fork 525
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
Paket convert-from-nuget adds paket.dependencies incorrectly to the solution file #2512
Comments
Indeed. I'll send another pull reqfefe. |
I wonder though, @forki: after my fix, why did all tests pass? |
because this is probably untested ... |
fsoikin
added a commit
to fsoikin/Paket
that referenced
this issue
Jul 11, 2017
… not present, or is empty. Fixes fsprojects#2512.
fsoikin
added a commit
to fsoikin/Paket
that referenced
this issue
Jul 11, 2017
… not present, or is empty. Fixes fsprojects#2512.
fsoikin
added a commit
to fsoikin/Paket
that referenced
this issue
Jul 11, 2017
… not present, or is empty. Fixes fsprojects#2512.
fsoikin
added a commit
to fsoikin/Paket
that referenced
this issue
Jul 11, 2017
… not present, or is empty. Fixes fsprojects#2512.
fsoikin
added a commit
to fsoikin/Paket
that referenced
this issue
Jul 11, 2017
… not present, or is empty. Fixes fsprojects#2512.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When using Paket 5.6.6, after running conversion from nuget on a solution with one project, the reference to the
paket.dependencies
is added in a way that the solution file fails to load.Repro steps
Create a solution with one project.
Create a
.paket
directory and put Paket 5.6.6 there.Run
.paket\paket convert-from-nuget
Run
.paket\paket auto-restore on
Try loading the solution in VS or Rider. Solution is not loaded.
Expected behavior
Solution should load and there should be a
.paket
solution folder added, withpaket.dependencies
file link in the solution folder.The solution file section should look like:
Actual behavior
The solution file is broken. It looks like this:
Known workarounds
Edit the solution file and move the line with
paket.dependencies
file inside theProjectSection
The text was updated successfully, but these errors were encountered: