Skip to content
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

Closed
alexeyzimarev opened this issue Jul 11, 2017 · 4 comments

Comments

@alexeyzimarev
Copy link

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, with paket.dependencies file link in the solution folder.

The solution file section should look like:

Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = ".paket", ".paket", "{3AC709DB-BDCA-4965-9004-52FC24A2425B}"
	ProjectSection(SolutionItems) = preProject
		..\paket.dependencies = ..\paket.dependencies
	EndProjectSection
EndProject

Actual behavior

The solution file is broken. It looks like this:

Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = ".paket", ".paket", "{3AC709DB-BDCA-4965-9004-52FC24A2425B}"
		..\paket.dependencies = ..\paket.dependencies
	ProjectSection(SolutionItems) = preProject
	EndProjectSection
EndProject

Known workarounds

Edit the solution file and move the line with paket.dependencies file inside the ProjectSection

@forki
Copy link
Member

forki commented Jul 11, 2017

I bet it's related to #2484 /cc @fsoikin

@fsoikin
Copy link
Contributor

fsoikin commented Jul 11, 2017

Indeed. I'll send another pull reqfefe.

@fsoikin
Copy link
Contributor

fsoikin commented Jul 11, 2017

I wonder though, @forki: after my fix, why did all tests pass?

@forki
Copy link
Member

forki commented Jul 11, 2017

because this is probably untested ...

fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 11, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 11, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 11, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 11, 2017
fsoikin added a commit to fsoikin/Paket that referenced this issue Jul 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants