Uh oh!
There was an error while loading. Please reload this page.
Microbuild Additions - #7
Conversation
| @@ -1,5 +1,6 @@ | |||
| { | |||
| "dependencies": { | |||
| "MicroBuild.Core": "0.2.0", | |||
There was a problem hiding this comment.
This makes me nervous that our official product assembly needs to depend on MicroBuild. Is this how other projects work in Roslyn?
There was a problem hiding this comment.
I believe so. See https://github.com/dotnet/roslyn-project-system/blob/master/src/Dependencies/Toolset/project.json for an example.
There was a problem hiding this comment.
But isn't the difference that there is just a random "toolset" project that depends on MicroBuild.Core, and here we are making our actual shipping assembly's project depend on MicroBuild.Core? The equivalent in my mind would be if https://github.com/dotnet/roslyn-project-system/tree/master/src/Microsoft.VisualStudio.ProjectSystem.Managed had a direct dependency on MicroBuild.Core.
basoundr
commented
Aug 3, 2016
This is only part of the change. We still need more Microbuild related things to get this project built in Microbuild. This Commit in Roslyn-PS is good starting point. |
333fred
commented
Aug 4, 2016
@dotnet-bot test Windows Debug |
333fred
commented
Aug 4, 2016
@dotnet-bot test Windows Debug |
333fred
commented
Aug 4, 2016
@dotnet-bot retest Windows Release |
| <?xml version="1.0" encoding="utf-8"?> | ||
| <Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> | ||
| <Choose> | ||
| <When Condition="'$(ProjectLanguage)' == 'VB'"> |
There was a problem hiding this comment.
Not sure we need this VB stuff, so we?
There was a problem hiding this comment.
I doubt we need it either, I've been copying from the Roslyn-project-system, and committed and pushed last night before I left. Still some more cleanup to do.
| <VersionPrefix Condition="'$(VersionPrefix)' == ''">1.0.0</VersionPrefix> | ||
| <!-- When running on Microbuild, this is set to "ymmdd.n". --> | ||
| <VersionSuffix Condition="'$(VersionSuffix)' == ''">$(BuildVersion)</VersionSuffix> |
There was a problem hiding this comment.
One thing to be careful about here is that nuget versions can't have a number as the first character after the -. So you always need some sort of alpha letter to start the prerelease ($(VersionSuffix)) part. Typically things like alpha, beta, preview, etc. These prerelease prefixes are usually checked into the repo, like the major, minor and patch numbers are.
333fred
commented
Aug 10, 2016
Because microbuild relies on the desktop version of msbuild, and we're running with the xplat version, we're not going to be able to use it directly. I'll be looking into how roslyn is doing signing, since they have to deal with this issue as well. I'll submit a new PR when I have something ready to review. |
Adding build scripts
Changes include: - Rename 'managed installations' to 'tracked installations' (dotnet#10) - Fix '.metadata' -> 'metadata' folder name (dotnet#18) - Include component type in error/warning messages (dotnet#11) - Remove component spec from runtime update (dotnet#12) - Remove GetInstallations wrapper (dotnet#6) - ScopedMutex throws TimeoutException on failure (dotnet#22) - Make InstallResult.Install non-nullable (dotnet#17) - Remove ComponentFilesExist shortcut (dotnet#19) - Wire up InstallSource enum (dotnet#21) - ListCommand: enum types, narrowed mutex, read-only verify, spacing (dotnet#3,dotnet#4,dotnet#5,#1) - Show global.json path in list output (dotnet#15) - Add doc comments to ListData types (dotnet#7) - Move SourceOption to CommonOptions, remove alias fields (dotnet#9) - Remove ResolveChannelFromGlobalJson test hook wrapper (dotnet#14) - Root 'dotnetup update' updates all components (dotnet#16) - GlobalJsonChannelResolver: support rollForward policy (dotnet#13) - Error when installing to unmanaged dotnet root (dotnet#20) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Changes include: - UpdateWorkflow.Execute returns non-zero exit code on failure (#1) - InfoCommand JSON output includes InstallSpecs (dotnet#2) - Wire --update-global-json through SdkUpdateCommand to UpdateWorkflow (dotnet#3) - Implement DotnetInstallManager.UpdateGlobalJson using Utf8JsonReader (dotnet#3) - Fix ResolveEntryDestPath to use normalized entry name (dotnet#4) - Fix test: MajorMinor test uses correct channel '9.0' (dotnet#5) - Fix test: LTS assertion checks Major instead of Minor (dotnet#6) - Fix ScopedMutex.Dispose to not leak mutex on ReleaseMutex throw (dotnet#7) - Make CommonOptions fields static readonly (dotnet#9) - Remove unused --no-progress from uninstall parsers (dotnet#10) - GarbageCollector catches Exception instead of just IOException (dotnet#11) - Capitalize 'SDK' in SdkCommandParser description (dotnet#12) - Eliminate redundant manifest reads in InstallerOrchestratorSingleton (dotnet#13) - Fix STS test error message to say 'major' not 'minor' (dotnet#14) - Make DotnetupUtilities.ExeSuffix readonly (dotnet#16) - Fix FormatBytes to use floating-point with one decimal (dotnet#17) - Remove dead ReleaseManifest variable in DotnetInstaller (dotnet#18) - Make UpdateChannel.Name immutable (dotnet#19) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…s manifest testfx split TerminalTestReporter.Summary.cs into focused partials (microsoft/testfx#10387), adding four upstream paths that the dotnet-test-terminal-reporter entry does not list. Until they are tracked, edits to the coverage, discovery, flaky-test and slowest-test rendering are invisible to the drift detector. The new sources are appended rather than sorted into the list: the drift bot keys issue identity on the positional source index, so inserting would orphan the open issues for .Summary.cs (dotnet#7) and .TestCompletion.cs (dotnet#8) and file duplicates at the shifted positions. Document that sources is append-only. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: b8858a93-4a8d-4028-b0db-c221ef158206
microsoft/testfx#10387 split TerminalTestReporter.Summary.cs into focused partials, adding Coverage, FlakyTests, SlowestTests and TestDiscovery. Upstream includes the folder with a glob, so nothing flagged the addition here and edits to those four files were invisible to the drift detector (microsoft/testfx#10390). Append the four paths to the dotnet-test-terminal-reporter entry, baselined at the split commit acb5bafaa2. They are appended rather than sorted in because the tracking-issue marker keys on the source index, and dotnet#7 (Summary) and dotnet#8 (TestCompletion) have open issues (dotnet#55472, dotnet#55473) that inserting would orphan. Those two keep their old baselines: their drift is real, unported feature work (retry/flaky accounting, in-process retry attribution), not just the move. Also bump source #0 (TerminalTestReporter.cs): the only upstream change since its baseline is a <remarks> comment describing upstream's partial layout, which needs no port into the SDK's single-file fork. Document both gotchas in eng/vendored-files.md. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3328d629-8443-45a7-8ee2-97d3ce23dee5
This adds the nuget dependency for building on MicroBuild, as well as installing our dotnet cli to the auto-cleaned folder when running on MicroBuild. Tagging @eerhardt for review. @basoundr, is there anything you can think of that we're missing for building?