Investigate interaction between `UseProxyToSpaDevelopmentServer` and `UseEndpoints`

[rafaelfgx]

[mkArtakMSFT]

@captainsafia, @JamesNK do you know if is this a newly added analyzer suggesting this change and is the proposed change truly equivalent to the original code?

[javiercn]

@rafaelfgx thanks for contacting us.

You shouldn't need to call app.UseRouting nor app.UseEndpoints if you are using minimal hosting (as you seem to be doing) as the host already wraps the pipeline with app.UseRouting and app.UseEndpoints.

You can call MapControllers directly on the builder. I believe mix and matching is not supported.

[brunolins16]

@rafaelfgx I have tested without app.UseRouting and app.UseEndpoints, as mentioned, and it should work. Can you share a repro?

Hi @rafaelfgx. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[halter73]

@brunolins16 Did you try with UseRouting but not UseEndpoints? That should also work.

[HarelM]

I've stumbled across this issue as well I believe as can be read in my comment here: #42937 (comment)
For some reason the commit is not in the post, the following is the relevant commit I did in order to revert back to a working state:
IsraelHikingMap/Site@419b98b
I did some workarounds as can be seen in the following commits:
IsraelHikingMap/Site@788a961
to bypass this but I believe the docs should mention the need to remove UseRouting as well so that developers will fix the warning properly without breaking the entire app like I did.
After the removal of UseRouting I believe the app is working as expected (although I'm not very confident it does as I have done some changes I don't fully understand)...