Skip to content

Conversation

@github-actions
Copy link
Contributor

[AUTOMATED]

twsouthwick and others added 25 commits July 14, 2025 11:29
This change adds more detail and consolidates existing topics to create
a more prescriptive and helpful set of options for developers looking to
migration their ASP.NET Framework to Core applications.

Main things included in this update are:

- Consolidated a topics that were logically connected into a single
  document
- Added some basic decision trees for developers to understand what is
  most likely to be useful to them
- Updated the initial landing page to provide a better overview of what
  challenges they may encounter as they start a migration
- Updated the setup instructions to align with the current state of
  things
Fixed date to required format with two digits.
Fixed ms.date format which requires 2 digit month
Just updated ms.date to current since file was significantly updated.
Expand ASP.NET Framework to Core migration
@guardrex
Copy link
Collaborator

guardrex commented Jul 19, 2025

@danroth27 ... Since the changes to the repo's settings, there's a regression in the live merge process.

Consider #35769, which made a change in a path from wwwwoot/index.html to wwwroot/index.html for the Blazor What's New content. That change for for the following INCLUDES file ...

https://github.com/dotnet/AspNetCore.Docs/blame/main/aspnetcore/release-notes/aspnetcore-10/includes/blazor.md#L140

When I merged the Merge-to-Live PR that we were discussing yesterday at #35764, that change did reach the What's New article. See the third paragraph immediately before the code sample at ...

https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-10.0?view=aspnetcore-9.0#client-side-fingerprinting

However, that PR (#35769) ... and the rest of them on that Merge-to-Live PR ... have re-appeared here on this new Merge-to-Live PR. They shouldn't be here. There should only be one PR here, which is the one that I just merged this morning (#35777).

Also, not that rebasing before merging matters, but I didn't expect there to be a rebase by default on these Merge-to-Live PRs (i.e., "Rebase and merge" button). I only expected a merge option (i.e., "Merge" button).

@danroth27
Copy link
Member

Also, not that rebasing before merging matters, but I didn't expect there to be a rebase by default on these Merge-to-Live PRs (i.e., "Rebase and merge" button). I only expected a merge option (i.e., "Merge" button).

OK, should be fixed now.

@guardrex guardrex merged commit 98a63f6 into live Jul 21, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants