"object reference." exception when we want to use it. If no one sets the Logger, it will be null and we will get an The system will workįine without this line, but it is best practice to use the property injection Thirdly, we set Logger to NullLogger.Instance. (inject) this property after creating the TaskAppService object. Secondly, we defined a public ILogger object named Logger. Logger.Info("Creating a new task with description: " + input.Description) įirst, we imported the namespace of Castle's ILogger interface. Public void CreateTask(CreateTaskInput input) 3: Do not write logs if no Logger supplied. 2: Getting a logger using property injection Public class TaskAppService : ITaskAppService Line: using //1: Import Logging namespace Same (thanks to Castle's common ILogger interface).įirst, we need to get a Logger object to write logs. No matter which logging library you choose, the code to write logs is the Seen in the configuration section), so you can easily change it to There is just a single-line of code for the dependency to log4net (as Templates come with Log4Net properly configured and ready to use. This way, you're independent from a specific logging libraryĪnd can easily change it later if needed. Castle provides a common interface for all It can work with different logging libraries: Log4Net, NLog, GitHub: /ABPFrameWorkGroup/AbpDocument2ChineseĪSP.NET Boilerplate uses Castle Windsor's logging.Chinese translations of ABP's documentation (thanks to all contributors).Email Sending (and MailKit Integration).Object To Object Mapping (and AutoMapper Integration).
0 kommentar(er)
