-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Merge to Live #35779
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
Merge to Live #35779
Conversation
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.
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Co-authored-by: Wade Pickett <[email protected]>
Expand ASP.NET Framework to Core migration
|
@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 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 ... 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). |
OK, should be fixed now. |
[AUTOMATED]