nlog

问题 I want to have a custom log class, which then injects its properties to nlog Logger. The class should initialize nlog target and config , and then others can use it without the need to know those details. public interface ILogger { void Log(LogEntry entry); } public enum LoggingEventType { Debug, Information, Warning, Error, Fatal}; public class LogEntry { public readonly LoggingEventType Level; public readonly string Message; public readonly Exception Ex; public LogEntry(LoggingEventType

问题 I am using Nlog v4.6.7 and render messages with the following layout (in Nlog.config). <layout xsi:type="JsonLayout" includeAllProperties="true"> <attribute name="timestamp" layout="${date:universalTime=true:format=yyyy-MM-dd HH\:mm\:ss,fff}" /> <attribute name="level" layout="${level}"/> <attribute name="message" layout="${message}" /> </layout> A typical logging is _logger.Info("Start {job} with {@data}", job, new {a,b,c}); I use the includeAllProperties option since each message may define

问题 I am integrating Nlog on an existing desktop application, to write logs to a shared folder. When running the application from Visual Studio, it writes files fine, both log file and internalLog file for debugging. But when I make a build and install it on the same machine it no longer writes the files. Edit: Language c#, and build using NSIS to create installers. Nlog.config is in the root folder of the project, and configuration (partial) <target name="file" xsi:type="File" fileName="file

问题 I am integrating Nlog on an existing desktop application, to write logs to a shared folder. When running the application from Visual Studio, it writes files fine, both log file and internalLog file for debugging. But when I make a build and install it on the same machine it no longer writes the files. Edit: Language c#, and build using NSIS to create installers. Nlog.config is in the root folder of the project, and configuration (partial) <target name="file" xsi:type="File" fileName="file

问题 Added to project.json file for logging: "Microsoft.Framework.Logging.NLog": "1.0.0-beta1" The Framework.Logging.NLog depends internally upon NLog, which I tried installing via Nuget, project.json, Package console. It doesn't help. Also wasn't able to find a way to configure NLog logging and a tutorial/guide to place the config sections of NLog. 回答1: NLog does not ship for CoreClr hence you need to define the dependency under aspnet50. Do look at the sample https://github.com/aspnet/Logging

问题 My app creates a log for the application itself, so record when it was activated, and what happened at an application level. The application is centered around 'profiles' - the user loads a profile which tells the application where/when/what/how. So I also want to create a log for each profile, to record the progress each time the profile is run. No problems so far... except that I want the profile log to be stored alongside the profile itself, so this means I need to configure NLog

问题 I would be grateful if someone could post me a sample nlog.config for using nlog with SQL Server Compact 4.0. I can output to the console and a file OK. I've tried various dbProviders and connectionStrings, but nothing seems to work. Thanks in advance. Alan T 回答1: I figured it out. My test application is a console application written in C#. Below is the contents of the various files I used. Program.cs using NLog; namespace ConsoleApplication2 { class Program { private static readonly Logger

问题 Is there a way to configure NLog to automatically log all exceptions my application can send? Currently I am going to all TRY/CATCH blocks and manually adding logging in the CATCH - but what if I miss some? And what if in the future someone else does Is there a way to tell NLog to just always log all exceptions? Esspecially some that are not caught and could cause a popup? 回答1: As far as I know, there is no way to confineNLog to log all exceptions. If all you want is to log unhandled

问题 I have 8 console projects in one solution(I'm planning to convert them to services in future) referencing each other. I'm planning to create a ILogger interface and Logger class to encapsulate Nlog methods as I don't want to reference nlog in every project. And pass this interface from Core project to every other as build parameter. Something like using Core ... ILogger logger = new Logger(); Questions are: 1) Can I use one config for every logger? I use ideas from here. Mainly caller info

问题 My application is pointing to .net core framework 1.1.1. I have added NLog to my project. NLog - 5.0.0-beta05 NLog.Config - 4.3.9 NLog.Extensions.Logging - 1.0.0-rtm-beta1 My NLog config file is as follows: <target name="infoInstrumentation" xsi:type="File" concurrentWrites="false" archiveFileName="/home/ubuntu/Desktop/Logs/Punu/ServiceInstrumentation.${shortdate}.{##}.log" archiveAboveSize="1000000" archiveNumbering="Rolling" maxArchiveFiles="10" fileName="/home/ubuntu/Desktop/Logs/Punu