Can't launch Kestrel if the startup takes 'long' time in Visual Studio 2022 .NET 6

[nicholasyin]

The screenshot explains. I just simulated the case when the startup might take a long time.

This error only happens when launching using Kestrel. With IIS Express it can allow a long startup time.

[nicholasyin]

Wonder if there's any options that I can change to tolerate this?

[davidfowl]

It works fine but the IDE is failing to launch the browser because the server isn't listening on the port as yet (because of the sleep). I don't think there's a way to tweak how long the Visual Studio will wait before it gives up on trying to connect to the application, but you can turn it off in Properties/launchSettings.json by setting "launchBrowser": false

cc @vijayrkn @BillHiebert

[nicholasyin]

I also tried with 8 seconds and it works. Anyway, the point is that I don't think my real startup code takes that long time. But the IDE appears to see so. I don't know where the time was spent, and also don't know from what point of time does the IDE start to count. From the successful build, or what. The process is very vague to me and I don't have a clue as to solving this.

[davidfowl]

I explained what the problem was and described a work around, did you try it?

[nicholasyin]

Yes, thanks for the workaround. I say it's a workaround, not a solution, because without the browser I can't know that the application is ready to accept request. Not quite convenient, but looks like it's the best that can be done, though.

[Tratcher]

because without the browser I can't know that the application is ready to accept request.

You'll know the server is ready to accept requests by looking at the console log output.

[nicholasyin]

because without the browser I can't know that the application is ready to accept request.

You'll know the server is ready to accept requests by looking at the console log output.

Well, that's true.

[Pilchie]

@davidfowl - what was the reason for re-opening? Do you see an action for us here?