Migrating pieces of dotnet/extensions to dotnet/aspnetcore

[JunTaoLuo]

I don't think I ever created an issue to track this work so I'll list out the work items below:

• Migrating sources from dotnet/extensions #19033 Move projects to aspnetcore:
  M.E.FileProviders.Embedded
  M.E.FileProviders.Embedded.Manifest.Task
  M.E.Configuration.KeyPerFile
  M.E.Localization
  M.E.Localization.Abstraction
  M.E.ObjectPool
  M.JSInterop
  M.JSInterop.JS
  M.E.WebEncoders
  M.E.Diagnostics.HealthChecks
  M.E.Diagnostics.HealthChecks.Abstractions
  M.A.Testing
  Shared sources
• Ensure we didn't miss any commits during the merge.
• Ensure currently open PRs are moved to aspnetcore: https://github.com/dotnet/extensions/pulls?q=is%3Aopen+is%3Apr+label%3Asource-migrated-to-aspnetcore
• Migrate aspnetcore components extensions#2974 Remove those projects from Extensions except M.A.Testing and Shared sources
• Decouple from dotnet/extensions razor#1620 Remove uses of removed extensions packages in aspnetcore-tooling
• Investigate splitting of Logging.Testing project
  • Removing from extensions Remove Serilog dependency in extensions extensions#3040
  • Moving LoggedTest to aspnetcore Migrate logging testing #19545
• Migrate relevant issues
• Post announcement
• Ensure Interop.JS artifacts published correctly
  • Tracking separately in Reference dotnet-js-interop by source #19300
• Ensure our docs are up to date (such as ops, readmes, etc) This will likely be updated as we notice errors in documentation instead.
• Make sure DARC subscriptions are correct
• Address Ingest extensions packages from dotnet/runtime extensions#3091 (comment)
• Address issues relating to the removed package dependencies from extensions ccf4cd0#r402145057 see discussion at Ingest updated packages from dotnet/runtime #20300 (comment) Addressed by Package references updates extensions#3179

[JunTaoLuo]

@anurse some of the remaining work will involve your input (such as triage and issue moving) so I'm assigning you as well.

[leus]

Sorry if I'm wasting your time - I cannot find a discussion regarding this move. Is there an issue where I can find the rationale or discussion prior to this move? (I use some of the affected components in a very critical piece of infrastructure, so I wonder what's going on.) Thanks.

[analogrelay]

We’re getting an announcement put together shortly! This is purely about where we build/maintain the code though. All the packages are continuing to ship in the same places (NuGet, for example) and same supported frameworks as before. If you have specific questions feel free to ask here for now.

[JunTaoLuo]

The announcement has been posted.

[smashedapples20]

Where is the announcement? Do you have a link?

[analogrelay]

Oops! Thanks for the reminder @smashedapples20 :). We posted the announcement but didn't link it in here. It's here: aspnet/Announcements#411

[JunTaoLuo]

Announcement for breaking changes was made in aspnet/Announcements#415.

[NullEntity]

@JunTaoLuo I was looking for the source for Config.Binder. It's at extensions/src/Configuration/Config.Binder/ in the last released tag, then extensions/src/Configuration only has Config.NewtonsoftJson on master. It doesn't look like it got migrated going through the aspnetcore commits. It looks like some stuff may have been removed from the extensions repo that shouldn't have been.

Edit: My friend told me they got migrated to dotnet/runtime. False alarm! I was confused because this was issue linked in the commit that removed them from extensions.