-
Couldn't load subscription status.
- Fork 129
Description
Is your feature request related to a problem? Please describe.
Definitely not a bug. Rather lack of abstraction/extensibility. I'd like to be able to customize file provisioning.
Particular use-case is: application needs to create log files in specific directory which is protected with specific permissions which launching account doesn't have assigned but application can access it using impersonalization.
Describe the solution you'd like
I suggest to let developers to specify a file provider which would allow to extend core functionality of file creation. Then use it on right places (e.g.
| Stream outputStream = _underlyingStream = System.IO.File.Open(path, FileMode.OpenOrCreate, FileAccess.Write, FileShare.Read); |
Describe alternatives you've considered
An alternative could be ability to inherit and extend core classes (e.g. FileSink) but from source code and issue comments it seems that's unwanted design.
Additional context