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

Extensions consolidation #32912

Merged
merged 606 commits into from
Mar 2, 2020
Merged

Conversation

maryamariyan
Copy link
Member

@maryamariyan maryamariyan commented Feb 27, 2020

  • Bring over commit history from Extensions repo
  • Thin out ported Extensions code by removing unused files
  • Enable incremental build of Extensions projects

wtgodbe and others added 30 commits August 22, 2019 15:09
…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
…ge/release/3.0-to-master

[automated] Merge branch 'release/3.0' => 'master'


Commit migrated from dotnet/extensions@12a28e4
…ge/release/3.0-to-master

[automated] Merge branch 'release/3.0' => 'master'


Commit migrated from dotnet/extensions@d8590b1
…ge/release/3.0-to-master

[automated] Merge branch 'release/3.0' => 'master'


Commit migrated from dotnet/extensions@fb7fdf5
- brings new Microsoft.Data.SqlClient version


Commit migrated from dotnet/extensions@3347747
@Dotnet-GitSync-Bot
Copy link
Collaborator

Note regarding the new-api-needs-documentation label:

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.

@jkotas
Copy link
Member

jkotas commented Feb 27, 2020

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.

@ericstj
Copy link
Member

ericstj commented Feb 27, 2020

Yes we plan to make these match the libraries structure.

@ericstj
Copy link
Member

ericstj commented Feb 29, 2020

Structure looks good in this one. I also spot checked "blame" on a few files and it looks the same between extensions and runtime. 👍 👍 👍

…tally

- BinPlacing for Extensions projects
- Ignore building Microsoft.Extensions. projects
- Use correct StringNameKeyId for Extensions projects
- Separate packaging path for extensions projects
- Add PreReleaseVersionIteration
@@ -8,6 +8,7 @@
<PatchVersion>0</PatchVersion>
<PreReleaseVersionLabel>preview</PreReleaseVersionLabel>
<PreReleaseVersionIteration>2</PreReleaseVersionIteration>
<PreReleaseVersionIteration Condition="$(MSBuildProjectName.StartsWith('Microsoft.Extensions.'))">$(PreReleaseVersionIteration)-runtime</PreReleaseVersionIteration>
Copy link
Member

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.

Copy link
Contributor

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>
Copy link
Member

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>
Copy link
Member

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.

Copy link
Member

@ericstj ericstj left a comment

Choose a reason for hiding this comment

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

LGTM

@maryamariyan maryamariyan merged commit e3ffd34 into dotnet:master Mar 2, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.