Enable Proxying step 4 generates an error

[cas-matt]

Description

app.ServiceProvider.GetRequiredService<IOptions>() generates an error message:

error CS1061: 'WebApplication' does not contain a definition for 'ServiceProvider' and no accessible extension method 'ServiceProvider' accepting a first argument of type 'WebApplication' could be found (are you missing a using directive or an assembly reference?)

Page URL

https://learn.microsoft.com/en-us/aspnet/core/migration/fx-to-core/inc/remote-app-setup?view=aspnetcore-9.0&pivots=manual

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/migration/fx-to-core/inc/remote-app-setup.md

Document ID

f3b2ce81-5438-1d1a-1c2b-6cc9a089a0ea

Platform Id

f8610778-e458-a8a6-8136-0ee8c72f11e8

Article author

@wadepickett

Metadata

• ID: f3b2ce81-5438-1d1a-1c2b-6cc9a089a0ea
• PlatformId: f8610778-e458-a8a6-8136-0ee8c72f11e8
• Service: aspnet-core
• Sub-service: migration

Related Issues

---

Associated WorkItem - 488325

[wadepickett]

@cas-matt, thanks verty much for raising this issue and relating your experience! We will get it fixed.

Notes:

The code example in the migration guide uses app.ServiceProvider which is no longer available in WebApplication instances. .

Possibly an error in step 4 of the "Enable Proxying" section of the remote-app-setup.md file. The code on line 139 uses app.ServiceProvider.GetRequiredService<IOptions>() which may be causing a compiler error since WebApplication doesn't have a ServiceProvider property.# Valid issue with incorrect code sample - Action needed

error CS1061: 'WebApplication' does not contain a definition for 'ServiceProvider' and no accessible extension method 'ServiceProvider' accepting a first argument of type 'WebApplication' could be found
This occurs because in ASP.NET Core, WebApplication doesn't expose a ServiceProvider property directly.

Action to consider but needs to be verified:
The code would be updated to use the proper way to access services from a WebApplication instance. Options include:

Using app.Services instead of app.ServiceProvider
Retrieving the options during app configuration before the app.Build() call

[cas-matt]

Hi wadepickett, we are trying to use the code from https://github.com/dotnet/systemweb-adapter as a model for our own code to port our app from ASP.NET web forms to ASP.NET core (or something like that). We are not having much success to mimic server conditions. The sample code works perfectly fine within the local host environment and proves that it is possible to use the ASP.NET framework login with the ASP.NET core. I have used most of the guidance you have in that article but have not had any luck getting the core side to pick up the framework login cookie. If you would like I can provide more feedback as to where we are failing.

[wadepickett]

@twsouthwick, I'm not as familiar with this area. Could you take a look and recommend what might be done here?

[twsouthwick]

Looks like there was a typo where it should have been Services rather than ServiceProvider. Opened a PR to fix the docs