You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Deepak Kumar (Jira)" <ji...@apache.org> on 2020/01/27 10:29:00 UTC

[jira] [Updated] (LOG4NET-643) Not logging in arbitrary location for UWP Application

     [ https://issues.apache.org/jira/browse/LOG4NET-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Deepak Kumar updated LOG4NET-643:
---------------------------------
    Description: 
Hi,

We need to logging in an arbitrary location for UWP application . For UWP application we are having only access to the particular location by default . If we need to access any other location then we need to use Storage Folder . Is there any other option  to  logging it in a specific folder for UWP Application now other than the default location.

  was:
Hi,

We need to logging in an arbitrary location for UWP application . For UWP application we are having only access to the particular location by default . If we need to access any other location then we need to use Storage Folder . is there any other option now to  logging it in a specific folder for UWP Application.


> Not logging in arbitrary location for UWP Application
> -----------------------------------------------------
>
>                 Key: LOG4NET-643
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-643
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 2.0.8
>            Reporter: Deepak Kumar
>            Priority: Blocker
>              Labels: patch, performance, windows
>             Fix For: 2.0.8
>
>
> Hi,
> We need to logging in an arbitrary location for UWP application . For UWP application we are having only access to the particular location by default . If we need to access any other location then we need to use Storage Folder . Is there any other option  to  logging it in a specific folder for UWP Application now other than the default location.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)