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

IncludeBuildOutput = false causes some issues #398

Open
wasabii opened this issue Oct 27, 2022 · 0 comments
Open

IncludeBuildOutput = false causes some issues #398

wasabii opened this issue Oct 27, 2022 · 0 comments

Comments

@wasabii
Copy link

wasabii commented Oct 27, 2022

I use a NoTargets project to generate a NuGet package that contains multiple different ProjectReference's build output. So, the generated nupkg has multiple files in lib/tfm. Seems a typical pattern.

NoTargets sets IncludeBuildOutput to false for obvious reasons: NoTargets projects don't have their own build output.

However, IncludeBuildOutput is used elsewhere in the SDK code. It is also used during pack in _WalkEachTargetFramework to determine whether or not to invoke $(TargetsForTfmSpecificBuildOutput) and $(TargetsForTfmSpecificDebugSymbolsInPackages). These two properties are generally used to do what I'm trying to do: include the build output of ProjectReferences into the Nuget package.

I haven't found anything wrong with setting IncludeBuildOutput to true. It doesn't break because of the missing primary output.

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

1 participant