WebApi migration - Githubissues

dotnet / upgrade-assistant

A tool to assist developers in upgrading .NET Framework applications to .NET 6 and beyond

MIT License

1.11k stars 163 forks source link

WebApi migration #60

Open mjrousos opened 3 years ago

mjrousos commented 3 years ago

More design is needed here; this could either be bringing back the web API compat shim or looking into what can be done with analyzers and code fixers

[ ] #1158
[ ] #1092
[ ] #1051
[ ] #1013
[ ] #897
[x] #684
[x] #683
[x] #682
[x] #680
[x] #673
[x] #672
[x] #660
[ ] #506
[ ] #498
[ ] #497
[ ] #494
[ ] #492
[ ] #360
[ ] #298
[ ] #277
[ ] #276
[ ] #275
[x] #242
[x] #241
[x] #90
[x] #78
[ ] #74
[x] #73
[ ] #71
[x] #70
[x] #68
[ ] #67
[x] #66
[x] #59

Additional issues that can be solved by Microsoft.AspNetCore.SystemWebAdapters:

[x] #1159
[x] #681
[x] #679
[x] #677
[x] #676
[x] #675
[x] #674
[ ] #503
[x] #500
[x] #496
[x] #495
[ ] #72

sunandabalu commented 2 years ago

@twsouthwick / @mjrousos Will these items listed here be taken care of with the symwebadapters?

/cc @brandonh-msft

twsouthwick commented 2 years ago

I've updated the list to separate things out as what is in scope at the moment for the web adapters. I'll close the issues that are currently solved, and transfer to the adapters repo the ones that remain open.

brandonh-msft commented 2 years ago

isn't this work for things to be brought in to UA, though? If they're over in webadapters that doesn't solve for the issue....

twsouthwick commented 2 years ago

If Upgrade Assistant brought in the adapters it would solve it for the issues that are supported by them.

brandonh-msft commented 2 years ago

Sure, but closing an issue opened in UA for UA to do a thing by putting that thing in another product (that isn't in UA) doesn't seem to be the appropriate process. The issue should remain open until WebAdapters is brought into UA (or we should create a new issue for that work & xfer all these issues over there)

twsouthwick commented 2 years ago

Would you prefer to reopen them or add an issue to integrate the adapters into the project?

brandonh-msft commented 2 years ago

I think we need to do 2 things:

[x] Create a User Story in UA to bring in WebAdapters [#1227]
[ ] Triage applicable items currently w/in UA as follows:
1. [ ] If it's a customer request, link to new/existing issue in WebAdapters (ensures traceability back into UA) and parent under new WebAdapters Item as a linked task (e.g. - [ ] ### syntax)
2. [ ] If it was an item put in by our team, move to WebAdapters

Have done the first one, but need you & @mjrousos to do Parts 2a and 2b