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

Version light command packages #5473

Merged
merged 3 commits into from
May 15, 2020
Merged

Version light command packages #5473

merged 3 commits into from
May 15, 2020

Conversation

chcosta
Copy link
Member

@chcosta chcosta commented May 13, 2020

Fixes https://github.com/dotnet/core-eng/issues/9825

Creates packages named via Arcade versioning semantics like

  • LightCommandPackages-5.0.0-ci.zip - local dev build

or

  • LightCommandPackages-5.0.0-ci-win-x64.zip - local dev build in a repo which defines an optional suffix via eng/AfterSolutionBuild.props

FYI @NikolaMilosavljevic

@@ -62,6 +62,7 @@
<VisualStudioSetupInsertionPath>$([MSBuild]::NormalizeDirectory('$(VisualStudioSetupOutputPath)', 'Insertion'))</VisualStudioSetupInsertionPath>
<VisualStudioSetupIntermediateOutputPath>$([MSBuild]::NormalizeDirectory('$(ArtifactsDir)', 'VSSetup.obj', '$(Configuration)'))</VisualStudioSetupIntermediateOutputPath>
<VisualStudioBuildPackagesDir>$([MSBuild]::NormalizeDirectory('$(VisualStudioSetupOutputPath)', 'DevDivPackages'))</VisualStudioBuildPackagesDir>
<LightCommandPackagesDir>$(ArtifactsDir)LightCommandPackages/</LightCommandPackagesDir>
<LightCommandObjDir>$(ArtifactsObjDir)/LightCommandPackages</LightCommandObjDir>
Copy link
Member

@tmat tmat May 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the right place for this definition? Seems very specific to Microsoft.DotNet.Build.Tasks.SharedFramework.Sdk, so I'd think the Sdk.props file of that package would be a better home for definitions of these properties.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a doc on what "light command packages" are? I'm also wondering why they need a specialized directory vs. just using the intermediate output directory of whatever project that uses the SDK.

Copy link
Member

@tmat tmat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

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

Successfully merging this pull request may close these issues.

3 participants