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
In .NET 8 the .NET SDK added support for a feature we're calling the 'artifacts output format', which is a centralized, simplified layout for project outputs that tackles several long-standing user reports about pain points working with 'standard' SDK artifact layouts. This layout was designed here and implemented here.
We need to document the new layout, how it's computed, how it's enabled, and how it can be customized.
Key points:
The feature is best configured through use of a Directory.Build.props file (new concept to a lot of folks, we have an easy way to get started with one in the CLI now)
The default layout is four levels only now: <root>/<artifact type>/<project name>/<pivots>
The feature has some properties that control its use:
UseArtifactsOutput - boolean property that controls if the feature is used at all
ArtifactsPath - string property that controls where the new 'root' of the layout will begin (defaults to a directory named 'artifacts' in the repo next to the Directory.Build.props (if any))
ArtifactsPivots - string property that allows for customizing the <pivots> the artifacts go into
defaults to a combination of TFM, Configuration, RID (dropping any of those that are not present)
We can reference the preview 3 and preview 4 blog post updates for this feature for content as well.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 47d5789d-4edb-3d22-9a8a-fdad704b8384
Version Independent ID: c92f0188-38cb-c658-5f1b-e2a3ce2d34e9
Uh oh!
There was an error while loading. Please reload this page.
Describe the new article
In .NET 8 the .NET SDK added support for a feature we're calling the 'artifacts output format', which is a centralized, simplified layout for project outputs that tackles several long-standing user reports about pain points working with 'standard' SDK artifact layouts. This layout was designed here and implemented here.
We need to document the new layout, how it's computed, how it's enabled, and how it can be customized.
Key points:
<root>/<artifact type>/<project name>/<pivots>
UseArtifactsOutput
- boolean property that controls if the feature is used at allArtifactsPath
- string property that controls where the new 'root' of the layout will begin (defaults to a directory named 'artifacts' in the repo next to the Directory.Build.props (if any))ArtifactsPivots
- string property that allows for customizing the<pivots>
the artifacts go intoWe can reference the preview 3 and preview 4 blog post updates for this feature for content as well.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 166836
The text was updated successfully, but these errors were encountered: