[QUERY] Must use Azure SignalR management SDK with Azure Functions, but no documentation exists. about azure-sdk-for-net HOT 7 CLOSED

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @chenkennt @sffamily @Y-Sindo.

from azure-sdk-for-net.

Now serverless hub is supported in isolated-process model. See https://github.com/aspnet/AzureSignalR-samples/tree/main/samples/DotnetIsolated-ClassBased for a sample. We are updating the docs.

from azure-sdk-for-net.

Thank you for the reply. I've switched to the class-based approach in the sample and it seems to be working.

One thing I wanted to mention:
If you add an HTTP trigger to your function using Visual Studio, a reference to Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore will be added to the project. It doesn't seem to be needed, but from what I can tell in my testing, if this package is present, the following error occurs when attempting to call "ConfigureFunctionWorkerDefaults":

The registration for method 'ConfigureFunctionsWebApplication' is expected for ASP.NET Core Integration.

The error goes away if ConfigureFunctionsWebApplication is added to the application, but if this is done, the Function App seems to no longer expose the endpoint /runtime/webhooks/signalr, which is needed for the connection to the Azure SignalR server.
Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore isn't actually needed to run HTTP triggers, so removing it is fine and everything seems to work. I'm just concerned that others may run into this and have a difficult time figuring it out.

This explanation probably sounds a little convoluted. If I can provide more information, please let me know.

Thanks again for the reply.

from azure-sdk-for-net.

@jsquire Could you help route the question about HTTP trigger in dotnet isolated process to related team?

Thank you for the reply. I've switched to the class-based approach in the sample and it seems to be working.

One thing I wanted to mention: If you add an HTTP trigger to your function using Visual Studio, a reference to Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore will be added to the project. It doesn't seem to be needed, but from what I can tell in my testing, if this package is present, the following error occurs when attempting to call "ConfigureFunctionWorkerDefaults":

The registration for method 'ConfigureFunctionsWebApplication' is expected for ASP.NET Core Integration.

The error goes away if ConfigureFunctionsWebApplication is added to the application, but if this is done, the Function App seems to no longer expose the endpoint /runtime/webhooks/signalr, which is needed for the connection to the Azure SignalR server. Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore isn't actually needed to run HTTP triggers, so removing it is fine and everything seems to work. I'm just concerned that others may run into this and have a difficult time figuring it out.

This explanation probably sounds a little convoluted. If I can provide more information, please let me know.

Thanks again for the reply.

from azure-sdk-for-net.

@jsquire Could you help route the question about HTTP trigger in dotnet isolated process to related team?

@michaeldaw: For discussion of the HTTP trigger in an isolated process, you'd want to open an issue with your inquiry in the azure-functions-dotnet-worker repository or open an Azure support request.

from azure-sdk-for-net.

Hi @michaeldaw. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

from azure-sdk-for-net.

@jsquire Will do, thank you.

from azure-sdk-for-net.