UWP applications have restricted access to the local file system and this can cause a few issues when using logging frameworks if you’re expecting to write logs to c:\\Temp
\nor %Temp% locations (for example).<\/p>\n
Your UWP application can write to the application’s installation folder, for example <\/p>\n
\r\nvar installedLocation = \r\n Windows.ApplicationModel.Package.Current.InstalledLocation.Path;\r\n<\/pre>\nanother alternatively is application data location, such as<\/p>\n
\r\nvar localFolder = \r\n ApplicationData.Current.LocalFolder.Path;\r\n\r\n\/\/ or\r\n\r\nvar localCache = \r\n ApplicationData.Current.LocalCacheFolder.Path;\r\n<\/pre>\nThese last two location will translate to a location such as the following, where username is the (as you’d expect) username the user logged into the machine with, and the GUID is the package family name GUID (taken from the application’s manifest). This is actually an extended GUID. <\/p>\n
\r\nC:\\Users\\<username>\\AppData\\Local\\Packages\\<guid>\r\n<\/pre>\nNote: At the time of writing I’m not sure where the string after the underscore which follows the GUID comes from.<\/em><\/p>\n
Let’s take a quick look at using Serilog’s File Sink to write our log files. Using NuGet install Serilog and Serilog.Sink.File and use the following code<\/p>\n
\r\nLog.Logger = _logger = new LoggerConfiguration()\r\n .WriteTo.File(\r\n new JsonFormatter(renderMessage: true),\r\n ApplicationData.Current.LocalCacheFolder.Path + "\\\\log.txt", \r\n rollingInterval: RollingInterval.Minute)\r\n .MinimumLevel.Verbose()\r\n .CreateLogger();\r\n<\/pre>\n