Fixed error on documentation tabs

[fjbelizon]

The tabs "In-Process" and "Isolated" were changed. The error is fixed with this changes.

[prmerger-automator]

@fjbelizon : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit b527e5c:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-app-configuration/enable-dynamic-configuration-azure-functions-csharp.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@zhenlan

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[zhenlan]

@fjbelizon can you please elaborate the reason for the change? What's the error?

[fjbelizon]

@zhenlan yes, of course. The tabs are changed. The information specifies, for example, the use of ‘ConfigureFunctionsWorkerDefaults()’ in Isolated Functions, however in this type of functions it is recommended to use ‘ConfigureFunctionsWebApplication()’ (at least if you use ASP.NET Core integration). Another problem is that the function ‘ConfigureFunctionsWorkerDefaults(app => app.UseAzureAppConfiguration())’ generates debugging problems, in functions that make use of context, such as Eternal Orchestration, etc. This is why the information in the ‘Isolated’ and ‘In-Proc’ tabs is wrong, the ‘In-Proc’ is the ‘Isolated’ and the ‘Isolated’ is the ‘In-Proc’.

[zhenlan]

@fjbelizon thanks. I'm not sure the content should be swapped. But before I dive into it, is this related to the issue you reported here Azure/AppConfiguration#915?

[fjbelizon]

Yes @zhenlan, the problems are related

[zhenlan]

@fjbelizon thanks for the confirmation. That issue is related to the durable functions. As discussed in Azure/AppConfiguration-DotnetProvider#484, it's more of an issue with middleware in durable.

To work around the issue, you can skip the call to UseAzureAppConfiguration, but get the refresher instance from the DI and call TryRefresh at the beginning of your function calls. This may be the reason you feel this document should swap the content for in-proc and isolated modes. There are far more differences for in-proc vs. isolated modes. If so, I believe this document is correct as is.

[fjbelizon]

I do not think so. That is why I have opened the documentation issue and the middleware issue. You can take whatever solution you want, I have reported the problem that exists. Thank you very much.

[American-Dipper]

@zhenlan - Should this PR remain open or can it be closed?

Thanks, PR review team

[zhenlan]

@American-Dipper this PR can be closed. I may see if there is any improvement/clarification I can make to this document later.

[fjbelizon]

I hope it will be done, because the documentation is not correct.