Application asp.net core 5 use websocket - VS 2022 version 17.2.3

Question

Application asp.net core 5 use websocket - VS 2022 version 17.2.3

sblb 1,231

I've created a new app web ASP.NET CORE 5 and by defaut there the statut 101 when I run it.
while before the update VS 17.04 forward 17.2.3 I didn't have this status! the status was at 200.

I think that the websocket must be set up.
I don't want to use it and I only want to use an API but the status 101 blocks my application with API.

I would like to know what status 101 is? apparently the websocket is put by default.

Have you an idea? Is it possible to disable it?

3 answers

Your answer

Answer 1

I don't want to use it and I only want to use an API but the status 101 blocks my application with API.

Turn off Hot Reload in Visual Studio. Debug -> "YourProjectName Debug Properties". Uncheck "Enable Hot Reload". Hot Reload does not block an API. Are you making an assumption or can you share code that illustrates how Hot Reload blocks an API?

I would like to know what status 101 is?

Simply Google status 101 to learn about the how web socket switching protocols works.

101 Switching Protocols

Answer 2

sblb 1,231

Hi, thanks to your answer.

Sorry, but I didn't see "Enable Hot Reload" in launch profile, why? in addition it prevents me to advance on another subject that you know.

Are you making an assumption or can you share code that illustrates how Hot Reload blocks an API?

This is not an assumption but only an observation!
Sorry, I didn't use the right word: it's not a block but a hold on the application.
Moreover, I am talking about an empty application without any action.

AgaveJoe 30,126 Reputation points

2022-06-07T12:37:57.007+00:00

Sorry, I didn't use the right word: it's not a block but a hold on the application.

Can you provide sample code and include the steps that illustrates a "hold on the application"?

Moreover, I am talking about an empty application without any action.

Hot reload debug options start with .NET 6. For .NET 5 you need to go to options.

Tools > Options > Projects and Solutions > ASP.NET Core > Auto build and refresh option

Select None. But, I don't think Hot Reload is the problem.

Answer 3

sblb 1,231

he problem appeared after the VS 2022 update to 17.2.3.
Now my application is not working anymore. Here you can find the link to my application : aspnet-core-server-side-processing-to-acces-to-the.html

I got the message MikeGebhard-6464 that's said :
The URL looks like a web socket connection not a Web API request.

And really I don't understand why I have a websocket connection and put the application on hold.

So I've creaed a you app to and I've already the on hold and websocket connection :

Tools > Options > Projects and Solutions > ASP.NET Core > Auto build and refresh option Select None.

I've tried to modify like you it does not change anything.

Is it possible to disable websocket?

AgaveJoe 30,126 Reputation points

2022-06-07T13:42:08.207+00:00

The web socket is in process. As far as I know, this is the expected behavior because the socket is open and essentially a communication pipeline between browser and web application. Make a change to the source code and you should see the browser refresh. This is a development tool that supposed to make your life easier.

Again, can you provide code that illustrates a "hold on the application". Perhaps there is an issue with your code???
sblb 1,231 Reputation points

2022-06-07T13:44:19.71+00:00

how do you want me to share my code? github?

all my code is here : aspnet-core-server-side-processing-to-acces-to-the.html
AgaveJoe 30,126 Reputation points

2022-06-07T13:58:11.697+00:00
how do you want me to share my code? github?

Actually, I think a better solution is for you to debug your own code. Rather than using the Visual Studio do start your unknown web project, use a CLI command to control how the application runs. Open a command prompt within the application's folder and enter...

dotnet run

Next, open the application in your browser. Most likely the URL is https://localhost:5001. You should no longer see the web socket connection. If your application still does not function as expected then there is a problem with your code. Use the Visual Studio debugger to figure out what's happening.
sblb 1,231 Reputation points

2022-06-07T15:04:59.837+00:00

you right! when I do dotnet run and I run my app and I didn't see web socket connection.

But after, I have any error when I use VS debbuger I see any error
AgaveJoe 30,126 Reputation points

2022-06-07T15:24:07.487+00:00

But after, I have any error when I use VS debbuger I see any error

You see an error in the Visual Studio debugger??? What is the error?

If I understand correctly, the original problem is sending an HTTP request to Web API. If the application behaves that same with dotnet run - that is you still cannot send an HTTP request - then the problem has nothing to do with the web socket connection. The purpose of testing with "dotnet run" is to determine if your observation is correct and the 101 status has put a "hold on the application".

Share via

Application asp.net core 5 use websocket - VS 2022 version 17.2.3

3 answers

Your answer