IHostingEnvironment object gets a difference in path

[netnr]

In the Linux system, the dotnet is started in different paths. The WebRootPath attribute of the IHostingEnvironment object is different from the ContentRootPath attribute. The dotnet startup path is obtained. Shouldn't it always be the path of the site directory?

CentOS7
dotnet --version 2.2.103

Code
https://github.com/netnr/test/blob/master/src/Netnr.Test/Controllers/PathController.cs

[John0King]

This is not a bug, It designed like this ,
the dotnet ***.dll start the app in the Terminal‘s current workDirectory (this will be the ContentRootPath)
and the WebRootPath is equal to ContentRootPath + '/wwwroot'

So in your first picture, the ContentRootPath is your workingDirectory and it can not find /wwwroot folder in it ,So WebRootPath is not point to wwwroot

[netnr]

If I want to upload an image to wwwroot/upload/image, how do I locate it? WebRootPath should be fixed to the wwwroot directory.

[John0King]

@netnr

1. you should rely on the IHostingEnvironment.WebRootPath and IHostingEnvironment.WebRootFileProvider
2. start your app in the site's directory

https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-2.2#create-the-service-file

The WorkingDirectory is important !

or

call .UseWebRoot("to your app's wwwroot folder ") at Program.Main your can set it to Path.Combin(AppContext.BaseDirectory,"wwwroot")

the default design allow you to use one app to run like different site , for example

D:/
|---YourApp
        |--- your app file 
|--- Site1Config      // if you run you app in this folder , it will use this folder's setting and wwwroot
        |----wwwroot
        |----appsetting.json
|--- Site2Config    // if you run you app in this folder , it will use this folder's setting and wwwroot
        |----wwwroot
        |----appsetting.json

[davidfowl]

The WebRootPath ends up being null when it doesn't physically exist. If you create the wwwroot folder then it'll show up.

[netnr]

Thank you very much, I already understand; but I still think that the WebRootPath property should always point to wwwroot

[davidfowl]

And the WebRootFileProvider will remain null?

[analogrelay]

This behavior is by design and we have no plans to change it.