Skip to content

Support nuget package restore more like how ClearScript.V8 looks like it’s supposed to #4

@binki

Description

@binki

I do not want to commit compiled assemblies and debugging files to my project’s repository if I am using ClearScript.Installer. The whole point of nuget and the new style of package restore is to avoid polluting your repo with precompiled binaries. That’s why there’s now a right way to restore nuget packages. ClearScript.V8 includes the native binaries to the packages folder but doesn’t set them as <Content/> items in the project. It has a script that’s supposed to update the .csproj with targets so that the native binaries get copied to the output directory without needing to be included in the project directly.

Maybe the right way would be to have an MSBuild target that adds the binaries as <Content/> items, but only during build (so that they are hidden from the VS UI). The <Content/> can directly reference where the binaries are stored in the nuget-managed packages folder. Then we can let whatever MSBuild rules there are for copying the binaries to the output directory go ahead as normal. I might experiment with this and see what I can get working.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions