Skip to content

Determine desired TFM behavior in a product build (+document?) #184

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

Closed
dagood opened this issue Sep 26, 2017 · 2 comments
Closed

Determine desired TFM behavior in a product build (+document?) #184

dagood opened this issue Sep 26, 2017 · 2 comments
Assignees

Comments

@dagood
Copy link
Member

dagood commented Sep 26, 2017

In #181 (comment) @eerhardt had some good questions about the source-built product:

[An arg [to tell a repo what TFM to build] makes sense to me.] It sounds like we'll need one for netstandard and one for netcoreapp.

Do we need both? I assumed the idea was that the whole source build would be for netcoreapp? /cc @weshaggard @ericstj

A really good/important question we need to figure out is: "What is the expected usage of these source-built assets?"

Do we expected people to reference the .nupkgs that are produced by this build? If so, then they won't be able to build any netstandard1.x projects. (Or even netstandard2.0 when we move to a netstandard2.1 or 3.0.) Is this intended?

I'm not 100% sure this is something that needs to be independently tracked/documented, but it's easy to close this issue if not.

@dseefeld
Copy link
Contributor

This will come into play when we address #210.

@weshaggard
Copy link
Member

Lets use #210 to track

@markwilkie markwilkie added this to the S136 May 21 - June 8 (5/21/2018) milestone May 26, 2018
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

5 participants