Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 40 million developers.
Sign up-
Microsoft
- Fargo, ND
Pro
-
Microsoft
- Fargo, ND
Pinned
1,022 contributions in the last year
Activity overview
Contribution activity
May 1, 2020
dagood has no activity
yet for this period.
April 2020
Created a pull request in dotnet/arcade that received 4 comments
Describe that CPDs are transitive in Darc.md
Add a section that teases apart this sentence to highlight important points I wasn't spotting: A dependency with a coherent parent will update its…
+6
−0
•
4
comments
- Delete task code that has been moved to the shared framework SDK in Arcade
- Consolidate Microsoft.NETCore.App property usage
- Enable the installer for mono Linux_x64
- [installer] Add RuntimeSpecificFrameworkSuffix property
- Adds support for generating Mono named NETCore.App Runtime Packs
- Creating a runtime pack artifacts directory in the libraries build
- Add build configuration to generate runtime packs for Android
- Add build configuration to generate runtime packs for iOS
Created an issue in dotnet/docs that received 8 comments
Remove .NET Core install docs for EOL distros
dotnet/runtime#34043
dotnet/release#331 (private repo)
@NikolaMilosavljevic @dleeapho
Document Details
8
comments
- Quality of life "darc clone --depth 0" improvements
- Fix "Detected package downgrade" when building 3.1.103.2-SDK using N-1 source-built or bootstrap flow
- Update 3.1 Version.Details.xml to work with strict coherency parent dependencies
- Support .NET 5.0 scenarios that require crossgen2 without using prebuilts from nuget.org
- Improve infra compatibility with Arcade in preparation to migrate to dotnet/installer
- Microsoft.AspNetCore.App symbols missing in 3.1 source-build
- Consume new strict CPDs in dotnet/installer for 5.0 source-build
- Handle non-standard repo URLs during 5.0 "darc clone"
- Determine repo build order during "darc clone" for arcade-powered source-build
- Investigate reason for /m:1 in core-setup and remove if possible

