Do you have a csproj file and a dependencies file (or just nuget package
name) for me to create a integration test?
On Nov 13, 2015 1:29 PM, "Thomas Heggelund" [email protected]
wrote:

When Paket installs a nuget package with
{packageid}.props/{packageid}.targets in build folder, it should

1. Put '' as the first
   child element in Project element
2. Put '' as the
   last child element in Project element

Paket puts both imports in the middle of csproj file and by doing so,
breaks compatiblity with nuget feature "Import MSBuild targets and props
files into project"

—
Reply to this email directly or view it on GitHub
#1219.

https://github.com/theggelund/paket_bug

does this work for you?

It worked in the test project and in some of my real projects but not all. I will try to analyze the ones that didn't work and try to create a new test project for you.

Updated https://github.com/theggelund/paket_bug

When nuget package is sorted after MultiTarget package => nunit
the import statement comes before nunit import

And I still have the initial issue with some projects.

Updated https://github.com/theggelund/paket_bug

Added a project called manual_project under MyClassLibrary. The initial issue is reproduced with the project. Used latest released paket 2.24.7

ok I fixed that Nunit issue

I hope it's not completely fixed.