Skip to content

Regression - paket install removing CopyToOutputDirectory property #1522

Description

Hi,
I was using version 2.51.4.0 before updating to 2.52.9.0. From now on, when I do paket install, my csproj included items go from:

<ItemGroup>  
<Content Include="filepath">  
  <Paket>True</Paket>  
  <CopyToOutputDirectory>Always</CopyToOutputDirectory>  
</Content>  
...
</ItemGroup>

To:

<ItemGroup>  
<Content Include="filepath">
  <Paket>True</Paket>
</Content>  
...
</ItemGroup>

Effectively removing my "CopyToOutputDirectory" directive... and breaking my build.

Activity

  1. forki commented on Mar 17, 2016

    @forki
    Member

    did you add that manually?

    what package are you using? Can I reproduce this?

  2. forki commented on Mar 17, 2016

    @forki
    Member

    mhm. then this is not really a regression. you were relying on a bug ;-)

    Anyways let's make that work. We need something like http://fsprojects.github.io/Paket/references-files.html#copy_local-settings for content files right?

  3. forki commented on Mar 21, 2016

    @forki
    Member

    so this is implemented. see http://fsprojects.github.io/Paket/nuget-dependencies.html#CopyToOutputDirectory-settings

    please let me know if this works for you

  4. forki commented on Mar 21, 2016

    @forki
    Member

    lol. I would appreciate a PR to the docs. ;-)

  5. tsibelman commented on Apr 3, 2016

    @tsibelman
    Contributor

    @forki Is copy_content_to_output_dir works if specified in line of specific dependency ?

  6. forki commented on Apr 3, 2016

    @forki
    Member

    it should.

  7. tsibelman commented on Apr 4, 2016

    @tsibelman
    Contributor

    Thank you, documentation is scarce on this

  8. tsibelman commented on Apr 4, 2016

    @tsibelman
    Contributor

    Another question, maybe this feature should not copy items that are of type Compile ?

  9. forki commented on Apr 4, 2016

    @forki
    Member

    please help to improve it.

    2016-04-04 15:55 GMT+02:00 tsibelman notifications@github.com:

    Thank you, documentation is scarce on this

    —
    You are receiving this because you were mentioned.
    Reply to this email directly or view it on GitHub
    #1522 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions