You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2017. It is now read-only.
The idea behind this feature is to make other things (csproj, assemblies) visible to vNext via project.json. Today, project.json can only reference other things that have a project.json or nuget packages. This doesn't change that but it allows other project types to be seen as a project.json based project without opting into the new compilation model.
Scenarios
Using a csproj as a project reference
Packing output from other project types (csproj) into a single nupkg
In the above example. We're building a single vnext class library with multiple outputs. The windows8 target framework will not be compiled but will instead use the pdb and dll specified for building the nuget package (kpm build)
The text was updated successfully, but these errors were encountered:
davidfowl
changed the title
Add support for exporting binaries from the project
Add support for including outputs from other project types
Jul 22, 2014
The idea behind this feature is to make other things (csproj, assemblies) visible to vNext via project.json. Today, project.json can only reference other things that have a project.json or nuget packages. This doesn't change that but it allows other project types to be seen as a project.json based project without opting into the new compilation model.
Scenarios
In the above example. We're building a single vnext class library with multiple outputs. The windows8 target framework will not be compiled but will instead use the pdb and dll specified for building the nuget package (kpm build)
The text was updated successfully, but these errors were encountered: