Application Works Perfectly in Visual Studio ,Not Working in IIS. What is the configurations does Visual Studio Follows ?

Question

Application Works Perfectly in Visual Studio ,Not Working in IIS. What is the configurations does Visual Studio Follows ?

Jayapandian, Krishnakumar 0

Hi,

I am Working on Project which uses GrpcWebSocketBridge.AspNetCore package availabe in Nuget.Org , I dont know the project works fine in Visual Studio Local Environment perfectly, But its not Working Properly when deployed in IIS (No deployment issues ,  Just not Working ). I have two question,

First Question : What are the Settings / Configuration does Visual Studio follows how its able run the project perfectly.

Second Question : What is the Server and configuration does it follow in Visual Studio to run an Web Application.

Lex Li (Microsoft) 6,032 Reputation points Microsoft Employee

2023-08-08T16:47:01.28+00:00

The differences are just too many, https://halfblood.pro/web-application-differences-in-visual-studio-and-iis-60fec7e311b3 You need to debug further into your web app.
Yurong Dai-MSFT 2,841 Reputation points Microsoft External Staff

2023-08-09T06:01:02.5866667+00:00

Hi @Jayapandian, Krishnakumar,

When you run a web application in Visual Studio, it typically uses the IIS Express web server for local debugging. IIS Express runs your web application in an application pool with its own settings, which manages configurations like authentication, authorization, URL routing, and more.

When you deploy your web application to IIS, please make sure that the IIS configuration (application pool, bindings, etc.) matches your application's expectations.

You need to gather more information about the problem, check the IIS server logs. Look for any error messages or warnings that might indicate the source of the problem.

2 answers

Your answer

Lex Li (Microsoft) 6,032 Reputation points Microsoft Employee

2023-08-08T16:47:01.28+00:00

The differences are just too many, https://halfblood.pro/web-application-differences-in-visual-studio-and-iis-60fec7e311b3 You need to debug further into your web app.
Yurong Dai-MSFT 2,841 Reputation points Microsoft External Staff

2023-08-09T06:01:02.5866667+00:00

Hi @Jayapandian, Krishnakumar,

When you run a web application in Visual Studio, it typically uses the IIS Express web server for local debugging. IIS Express runs your web application in an application pool with its own settings, which manages configurations like authentication, authorization, URL routing, and more.

When you deploy your web application to IIS, please make sure that the IIS configuration (application pool, bindings, etc.) matches your application's expectations.

You need to gather more information about the problem, check the IIS server logs. Look for any error messages or warnings that might indicate the source of the problem.

Answer 1

Jayapandian, Krishnakumar 0

Hi @Yurong Dai-MSFT ,

                                 Yes you are Correct , Visual Studio Runs on IIS Express only if IIS Express is configured in launchSettings.json file ,But  In my project its configured for dotnetrunMessages and application url.

Yurong Dai-MSFT 2,841 Reputation points Microsoft External Staff

2023-08-10T06:32:29.1666667+00:00
Yes, the launchSettings.json file is a unique configuration standard for ASP.NET Core applications, which is used for application startup preparations, including environment variables, development ports, etc. This file sets up the different environments in which Visual Studio can start.

The configuration file adds two nodes by default, where "iisSettings" is used to set IIS-related options, and the "profiles" node defines a series of Profiles used to represent application startup scenarios. The initial launchSettings.json file will create two Profiles by default, one is named "IIS Express" and the other is named using the current project name (for example: NET5.Api").

Each Profile is equivalent to defining the startup scene of the application. The related settings include the application startup method, environment variables and URL, etc. The specific settings include:

iisSettings is the configuration of IIS:

windowsAuthentication: Whether IIS enables Windows Authentication.

anonymousAuthentication: Whether IIS enables anonymous authentication.

applicationUrl: Specifies the address of the IIS server.

sslPort: Specify the https port of the IIS server.

IIS Express configuration in profiles:

launchBrowser: A Boolean switch indicating whether to automatically launch the browser when the application is launched.

launchUrl: If launchBrowser is set to true, the initialization path used by the browser is set through this property.

environmentVariables: This attribute is used to set environment variables. ASP.NET Core applications use such an environment variable to represent the current deployment environment. The configuration of multiple environments can be switched through ASPNETCORE_ENVIRONMENT.

commandName: The type of command to start the current application. Valid options include IIS, IISExpress, and Project. The first three options indicate that IIS, IISExpress, and the specified executable file (.exe) are used to start the application. If we use the dotnet run command to start the program, the corresponding Profile startup name should be set to Project.

applicationUrl: A list of URLs used by the application. Multiple URLs are separated by semicolons (";").

NET5.Api configuration in profiles:

Compared with IIS Express, there is one more dotnetRunMessages here, which is a Boolean value that determines whether to give feedback at runtime.

Answer 2

the typical issue with running under IIS is the service account, permissions and runtime environment (running as a service).

when run in VS as either an app or its express the appp is running under your account with your permissions. another difference, is that the app is running under logged in windows account, so has access to the windows gui (say MessageBox), and the users profile is loaded into the registry (printer list, mapped drives, etc).

the other common error is configuration (use of localhost, etc).

note: the GrpcWebSocketBridge.AspNetCore package should only be effected by configuration. also the server hosting IIS must support web sockets:

https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-websocket-protocol-support

Share via

Application Works Perfectly in Visual Studio ,Not Working in IIS. What is the configurations does Visual Studio Follows ?

2 answers

Your answer