Today, I accidentally found a change because I haven't seen the. net core project for a long time. I found that the default port for project startup is not 5000. I remember clearly that when it was version 1. X of. net core, the default port number for each startup was 5000, but not now. Take this opportunity to talk about the solution to modify the default port number of the. net core project. The most familiar solution is to use the UseUrls() method to configure the port to be used when directly creating the WebHost object in Program.cs, as shown below:
This is the most familiar modification method. After startup, ports 5001 and 5002 will start listening, so we will visit our website through these two addresses. However, the disadvantage of this method is that we need to modify the code and recompile it for operation. This is not the best solution we want. If it can be configured directly in the configuration file, it is perfect. I saw a method in a personal blog, address: http://benfoster.io/blog/how-to-configure-kestrel-urls-in-aspnet-core-rc2 Add a JSON file called hosting.json, which means service configuration. Of course, the name doesn't matter. Only one node needs to be added. The contents are as follows:
<span style="font-size:14px;">{
"server.urls": "http://localhost:5001;http://localhost:5002"
}</span>Add a server.urls node, and then modify the Program.cs file,
After operation, the display is as follows:
Both ports 5001 and 5002 have listening enabled.
This aroused my interest and turned to the source code about this piece. About the source code address of Hosting: https://github.com/aspnet/Hosting
Next, let's go deep into the reasons and check the Build method of IWebHost interface:
-
/// <summary>
-
/// Builds the required services and an <see cref="IWebHost"/> which hosts a web application.
-
/// </summary>
-
public IWebHost Build()
-
{
-
if (_webHostBuilt)
-
{
-
throw
new InvalidOperationException(Resources.WebHostBuilder_SingleInstance);
-
}
-
_webHostBuilt =
true;
-
-
var hostingServices = BuildCommonServices(
out
var hostingStartupErrors);
-
var applicationServices = hostingServices.Clone();
-
var hostingServiceProvider = GetProviderFromFactory(hostingServices);
-
-
if (!_options.SuppressStatusMessages)
-
{
-
// Warn about deprecated environment variables
-
if (Environment.GetEnvironmentVariable(
"Hosting:Environment") !=
null)
-
{
-
Console.WriteLine(
"The environment variable 'Hosting:Environment' is obsolete and has been replaced with 'ASPNETCORE_ENVIRONMENT'");
-
}
-
-
if (Environment.GetEnvironmentVariable(
"ASPNET_ENV") !=
null)
-
{
-
Console.WriteLine(
"The environment variable 'ASPNET_ENV' is obsolete and has been replaced with 'ASPNETCORE_ENVIRONMENT'");
-
}
-
-
if (Environment.GetEnvironmentVariable(
"ASPNETCORE_SERVER.URLS") !=
null)
-
{
-
Console.WriteLine(
"The environment variable 'ASPNETCORE_SERVER.URLS' is obsolete and has been replaced with 'ASPNETCORE_URLS'");
-
}
-
}
-
-
var logger = hostingServiceProvider.GetRequiredService<ILogger<WebHost>>();
-
// Warn about duplicate HostingStartupAssemblies
-
foreach (
var assemblyName
in _options.GetFinalHostingStartupAssemblies().GroupBy(a => a, StringComparer.OrdinalIgnoreCase).Where(g => g.Count() >
1))
-
{
-
logger.LogWarning(
$"The assembly {assemblyName} was specified multiple times. Hosting startup assemblies should only be specified once.");
-
}
-
-
AddApplicationServices(applicationServices, hostingServiceProvider);
-
-
var host =
new WebHost(
-
applicationServices,
-
hostingServiceProvider,
-
_options,
-
_config,
-
hostingStartupErrors);
-
try
-
{
-
host.Initialize();
-
-
return host;
-
}
-
catch
-
{
-
// Dispose the host if there's a failure to initialize, this should clean up
-
// will dispose services that were constructed until the exception was thrown
-
host.Dispose();
-
throw;
-
}
-
private void EnsureServer()
-
{
-
if (Server ==
null)
-
{
-
Server = _applicationServices.GetRequiredService<IServer>();
-
-
var serverAddressesFeature = Server.Features?.Get<IServerAddressesFeature>();
-
var addresses = serverAddressesFeature?.Addresses;
-
if (addresses !=
null && !addresses.IsReadOnly && addresses.Count ==
0)
-
{
-
var urls = _config[WebHostDefaults.ServerUrlsKey] ?? _config[DeprecatedServerUrlsKey];
-
if (!
string.IsNullOrEmpty(urls))
-
{
-
serverAddressesFeature.PreferHostingUrls = WebHostUtilities.ParseBool(_config, WebHostDefaults.PreferHostingUrlsKey);
-
-
foreach (
var
value
in urls.Split(
new[] {
';' }, StringSplitOptions.RemoveEmptyEntries))
-
{
-
addresses.Add(
value);
-
}
-
}
-
}
-
}
-
}
It is not difficult to find the URL address added in the above method. In this line of code:
var urls = _config[WebHostDefaults.ServerUrlsKey] ?? _config[DeprecatedServerUrlsKey];
W according to the URL judgment here, if the current default configuration is empty, the following configuration will be used, and the deprecated serverurlskey has been defined at the beginning,
private static readonly string DeprecatedServerUrlsKey = "server.urls";
The default value of this parameter is server.urls, so we directly configure this key value pair in hosting.json. After. net core starts, it will automatically read the configuration file and use the configured port. Careful partners will find that in the source code, there are two other points about configuring URLs. One is in the Build method above, and there is one judgment:
-
if (Environment.GetEnvironmentVariable(
"ASPNETCORE_SERVER.URLS") !=
null)
-
{
-
Console.WriteLine(
"The environment variable 'ASPNETCORE_SERVER.URLS' is obsolete and has been replaced with 'ASPNETCORE_URLS'");
-
}
If aspnetcore is in the environment variable_ If server.urls is not empty, this value will replace aspnetcore_ In addition, there is a judgment code in the constructor of WebHostBuilder
-
if (
string.IsNullOrEmpty(GetSetting(WebHostDefaults.ServerUrlsKey)))
-
{
-
// Try adding legacy url key, never remove this.
-
UseSetting(WebHostDefaults.ServerUrlsKey, Environment.GetEnvironmentVariable(
"ASPNETCORE_SERVER.URLS"));
-
}
If the value of URLs in the obtained default configuration is null, aspnetcore is enabled_ The configuration in the server.urls environment variable also tells us that we can also put the startup port into the environment variable, right-click the project attribute and select debug,
Add environment variable ASPNETCORE_SERVER.URLS configuration. The above is all the methods I summarized to modify the default startup port. If there are other methods, please leave a message.
good night.
Scan the two-dimensional code, pay attention to my official account, learn together and make progress together!