Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BasePath directory not created when outside the current providers directory #1

Closed
DoCode opened this issue Nov 7, 2017 · 1 comment
Labels

Comments

@DoCode
Copy link

DoCode commented Nov 7, 2017

When BasePath is relative upwards the current file providers directory then the directory and logs not created.

Sample:

  "logging": {
    "BasePath": "..\\appdata\\logs",
    "EnsureBasePath": true,
    // ...
@adams85
Copy link
Owner

adams85 commented Nov 22, 2017

This is the expected behavior as default implementation is built on the top of PhysicalFileProvider. This is explained in the MSDN docs: "When instantiating this provider, you must provide it with a directory path, which serves as the base path for all requests made to this provider (and which restricts access outside of this path)."

Anyway, readme docs is updated to remark on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants