Skip to content

More build output changes#15470

Merged
jaredpar merged 5 commits intodotnet:masterfrom
jaredpar:fix-output
Nov 23, 2016
Merged

More build output changes#15470
jaredpar merged 5 commits intodotnet:masterfrom
jaredpar:fix-output

Conversation

@jaredpar
Copy link
Member

Changes:

  • Remove ProducesNoOutput usage as it's no longer needed. In every case Settings.props or Versions.props can be imported directly
  • Remove Dependencies.sln as it's no longer used.
  • Remove unnecessary extra files in MicroBuild.

@jaredpar
Copy link
Member Author

CC @jasonmalinowski, @dotnet/roslyn-infrastructure

Copy link
Member

@jasonmalinowski jasonmalinowski left a comment

Choose a reason for hiding this comment

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

Just some questions to make the code more self-documenting.

<!-- NuGet version -->
<NuGetReleaseVersion>$(RoslynFileVersionBase)</NuGetReleaseVersion>
<NuGetPerBuildPreReleaseVersion>$(NuGetPreReleaseVersion)-$(BuildNumberFiveDigitDateStamp)-$(BuildNumberBuildOfTheDayPadded)</NuGetPerBuildPreReleaseVersion>
<NuGetPackageRoot Condition="'$(NuGetPackageRoot)' == ''">$(NUGET_PACKAGES)</NuGetPackageRoot> <!-- Respect environment variable if set -->
Copy link
Member

Choose a reason for hiding this comment

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

Could you add a comment to the file explaining why it's in Versions.props? This seems like it really should be in Settings.props where it was.

Copy link
Member Author

Choose a reason for hiding this comment

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

A considerable portion of the values defined in Version.props, and by extension Dependencies.props, are NuGet packages. Not having the root for which to find them reduced the values of these files.

Importing Settings.props is a bit of a heavier hand is it brings along a lot of properties which are specific to building. There are a number of build files that are just tooling that can't always import these values. Hence I broke it up this way.

I've tried to document the intent of these files in the following README.md. Happy to update if you feel necessary

https://github.com/dotnet/roslyn/blob/master/build/Targets/README.md

Copy link
Member

@tmat tmat Nov 22, 2016

Choose a reason for hiding this comment

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

"Microsoft.CodeAnalysis.Analyzers",
"Microsoft.VisualBasic",
"Microsoft.Composition",
"MicroBuild.*",
Copy link
Member

Choose a reason for hiding this comment

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

Where is it documented what this does?

Copy link
Member Author

Choose a reason for hiding this comment

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

Latest commit on this PR updated the README.md for RepoUtil to describe this section.

@jaredpar jaredpar merged commit b3962dc into dotnet:master Nov 23, 2016
@jaredpar jaredpar deleted the fix-output branch November 23, 2016 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants