Expand ASP.NET Framework to Core migration #35755
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
aspnetcore/migration/fx-to-core/areas/session/samples/serialization/Program_Custom.cs
Outdated
Show resolved
Hide resolved
aspnetcore/migration/fx-to-core/areas/session/samples/remote/Global.asax.cs
Outdated
Show resolved
Hide resolved
|
@tdykstra @wadepickett ... I'll have a little time before EOW. Do you want me to review this, or do you want to take care of it? |
aspnetcore/migration/fx-to-core/areas/claimsprincipal-current.md
Outdated
Show resolved
Hide resolved
aspnetcore/migration/fx-to-core/areas/claimsprincipal-current.md
Outdated
Show resolved
Hide resolved
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]>
|
@wadepickett thanks! I've committed those suggestions and updated the ms.date values. let me know if there's more I need to do here |
|
I'll remove myself as a reviewer because @wadepickett is taking care of this one. |
|
@wadepickett @twsouthwick ... Do you see a "Restore Branch" button in your UI here? I don't see one, but I'm wondering if you do. |
|
BTW @twsouthwick ... Your fork's main branch is quite stale ... 8,000 commits behind us ... |
I deleted it once it was merged
yeah, I don't use that main branch - I have the upstream branch set to the one from dotnet and just ignore the one on mine |
|
In theory, we can still restore that branch to work on it for whatever is breaking the build. |
|
Sorry, there is no "Restore Branch" button on my end. Yes, it shows deleted after being merged. There was only the option for reverting merge for me. |
|
We might want to do these in smaller chunks going forward where possible. |
|
Ok ... thought so. In theory, it can still be done. For now, let's see what effect this has ... Probably no effect, but it was a complaint on that PR's build result. |
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:
document
most likely to be useful to them
challenges they may encounter as they start a migration
things
Fixes #35755
Internal previews
Toggle expand/collapse