-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Extensions consolidation #32912
Extensions consolidation #32912
Conversation
maryamariyan
commented
Feb 27, 2020
•
edited
Loading
edited
- Bring over commit history from Extensions repo
- Thin out ported Extensions code by removing unused files
- Enable incremental build of Extensions projects
…ge/release/3.0-to-master [automated] Merge branch 'release/3.0' => 'master' Commit migrated from dotnet/extensions@14efea2
…ge/release/3.0-preview9-to-release/3.0 [automated] Merge branch 'release/3.0-preview9' => 'release/3.0' Commit migrated from dotnet/extensions@a459d9e
…ge/release/3.0-to-master [automated] Merge branch 'release/3.0' => 'master' Commit migrated from dotnet/extensions@a070a81
Commit migrated from dotnet/extensions@c731d57
- no-op merge, no reason to wait Commit migrated from dotnet/extensions@7f64f14
…#2080) Commit migrated from dotnet/extensions@4254b86
…/3.0 Commit migrated from dotnet/extensions@07c506d
…ns#2226) - no-op merge Commit migrated from dotnet/extensions@44f2dd8
- no-op merge Commit migrated from dotnet/extensions@8f37920
Commit migrated from dotnet/extensions@887ce4f
- no-op merge Commit migrated from dotnet/extensions@39d5064
Commit migrated from dotnet/extensions@3940ade
- brings newer Arcade Commit migrated from dotnet/extensions@4afab35
Commit migrated from dotnet/extensions@8b04320
Commit migrated from dotnet/extensions@7f4859e
…ge/release/3.0-to-master [automated] Merge branch 'release/3.0' => 'master' Commit migrated from dotnet/extensions@12a28e4
Commit migrated from dotnet/extensions@033ea04
…ge/release/3.0-to-master [automated] Merge branch 'release/3.0' => 'master' Commit migrated from dotnet/extensions@d8590b1
Commit migrated from dotnet/extensions@ae3a22b
…ge/release/3.0-to-master [automated] Merge branch 'release/3.0' => 'master' Commit migrated from dotnet/extensions@fb7fdf5
Commit migrated from dotnet/extensions@f8ba700
- no-op merge Commit migrated from dotnet/extensions@b7f895d
Commit migrated from dotnet/extensions@5dbc609
- no-op merge Commit migrated from dotnet/extensions@04a22bf
Commit migrated from dotnet/extensions@d838533
- brings new Microsoft.Data.SqlClient version Commit migrated from dotnet/extensions@3347747
Commit migrated from dotnet/extensions@2220e1a
- no-op merge Commit migrated from dotnet/extensions@3f880fd
- new Arcade Commit migrated from dotnet/extensions@c2147ae
Commit migrated from dotnet/extensions@321a30c
Commit migrated from dotnet/extensions@d525539
These lines were removed unexpectedly by the automated file header code fix. Commit migrated from dotnet/extensions@738f2d6
Switch to MIT license Commit migrated from dotnet/extensions@f406602
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
Are we also going to fix the directory structure to follow the libraries conventions? I guess it may be part of the "making the build work" because the build scripts assume the convention in number of places. |
Yes we plan to make these match the libraries structure. |
0e6d7fd
to
091eee0
Compare
Structure looks good in this one. I also spot checked "blame" on a few files and it looks the same between extensions and runtime. 👍 👍 👍 |
091eee0
to
1650655
Compare
…tally - BinPlacing for Extensions projects - Ignore building Microsoft.Extensions. projects - Use correct StringNameKeyId for Extensions projects - Separate packaging path for extensions projects - Add PreReleaseVersionIteration
6264b65
to
3df8292
Compare
@@ -8,6 +8,7 @@ | |||
<PatchVersion>0</PatchVersion> | |||
<PreReleaseVersionLabel>preview</PreReleaseVersionLabel> | |||
<PreReleaseVersionIteration>2</PreReleaseVersionIteration> | |||
<PreReleaseVersionIteration Condition="$(MSBuildProjectName.StartsWith('Microsoft.Extensions.'))">$(PreReleaseVersionIteration)-runtime</PreReleaseVersionIteration> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JunTaoLuo here's the workaround we're going to use temporarily to permit package overlap between extensions and runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good
<ProjectExclusions Include="$(MSBuildThisFileDirectory)*\ref\**\Microsoft.Extensions.*proj" Exclude="@(PortedExtensionsProject)" /> | ||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)*\src\**\Microsoft.Extensions.*proj" Exclude="@(PortedExtensionsProject)" /> | ||
<ProjectExclusions Include="$(MSBuildThisFileDirectory)*\tests\**\Microsoft.Extensions.*.Tests.csproj" Exclude="@(PortedExtensionsProject)" /> | ||
</ItemGroup> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice place to put the central workaround for the traversal projects while you bring them up 👍 👍 👍
@@ -311,6 +322,9 @@ | |||
<!-- Paths to binplace package content --> | |||
<NETCoreAppPackageRefPath>$(ArtifactsBinDir)pkg\$(NetCoreAppCurrent)\ref</NETCoreAppPackageRefPath> | |||
<NETCoreAppPackageRuntimePath>$(ArtifactsBinDir)pkg\$(NetCoreAppCurrent)\lib</NETCoreAppPackageRuntimePath> | |||
|
|||
<ASPNETCoreAppPackageRefPath>$(ArtifactsBinDir)pkg\aspnetcoreapp\ref</ASPNETCoreAppPackageRefPath> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could use a comment, but you can add it when you submit the PR that introduces the extensions transport package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM