Autofac.Extras.NLog | Autofac module to integrate Autofac | Dependency Injection library

by ziyasal C# Version: v2.0.0-rc License: MIT

X-Ray Key Features Code Snippets(3)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | Autofac.Extras.NLog Summary

Autofac.Extras.NLog is a C# library typically used in Programming Style, Dependency Injection applications. Autofac.Extras.NLog has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

An Autofac module to integrate Autofac and NLog, it supports both constructor and property injection.

Support

Quality

Security

License

Reuse

Support

Autofac.Extras.NLog has a low active ecosystem.

It has 47 star(s) with 19 fork(s). There are 8 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 8 have been closed. On average issues are closed in 88 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Autofac.Extras.NLog is v2.0.0-rc

Quality

Autofac.Extras.NLog has 0 bugs and 0 code smells.

Security

Autofac.Extras.NLog has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Autofac.Extras.NLog code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Autofac.Extras.NLog is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Autofac.Extras.NLog releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Autofac.Extras.NLog saves you 1414 person hours of effort in developing the same functionality from scratch.

It has 3162 lines of code, 0 functions and 11 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Autofac.Extras.NLog

Get all kandi verified functions for this library.

Autofac.Extras.NLog Key Features

No Key Features are available at this moment for Autofac.Extras.NLog.

Autofac.Extras.NLog Examples and Code Snippets

Autofac Loggging Module for NLog,Register SimpleNLogModule to Autofac

Lines of Code : 23

License : Permissive (MIT)

Copy

containerBuilder.RegisterModule();

public class SampleClassWithConstructorDependency : ISampleInterface
{
    private readonly ILogger _logger;

    public SampleClassWithConstructorDependency(ILogger logger)
    {
      _logger = logger;
  }

Autofac Loggging Module for NLog

Lines of Code : 1

License : Permissive (MIT)

Copy

Install-Package Autofac.Extras.NLog

Autofac Loggging Module for NLog,Register NLogModule to Autofac

Lines of Code : 1

License : Permissive (MIT)

Copy

containerBuilder.RegisterModule();

Community Discussions

Trending Discussions on Autofac.Extras.NLog

Backup catching for exception thrown in EventHandler

Autofac Property Injection in already registered service

QUESTION

Backup catching for exception thrown in EventHandler

Asked 2019-Dec-10 at 12:15

I have a C# Program running as a Windows service doing some Network shenanigans I thought I had last-ditch "Log Fatal Errors" handling set up. But I've come across an edge case where the Service ends up dead but dodges those catches. :(

I believe this is caused by code throwing an Exception in the EventHandler registered to a .NET library's event.

Obviously I can (andshould!) catch the Exception in my handler, but I'd like to understand how this is avoiding my fall-back error handling, and whether I can add some even more robust fall back logging, to ensure that I have some log records to analyse similar silent bugs in future.

The punchline of relevant code isn't terribly complex:

ServiceBase.Run(container.Resolve()); in a try ...catch in Program.Main() MyProjectWindowsService : ServiceBase is the service object with an OnStop() implmentation. NetworkChange.NetworkAvailabilityChanged += CodeThatThrows;

But when that Exception is thrown, neither OnStop() nor the try...catch trigger. I can get it in a debugger, and it doesn't seem to go anywhere .. it just ... stops.

Fuller program details below, if you want them.

How can I catch and log unhandled exceptions in Event Handlers registered to external library events?

(Also ... Is the behaviour I've described above the expected behaviour, or is there something slightly weird happening?)

Program EXE entry point:

...

ANSWER

Answered 2019-Dec-10 at 11:49

I unfortunately can only speculate why the exception isn't being caught by your code (and I've kept that speculation to the comments)

However 2 events that might help you are,

AppDomain.UnhandledException - this allows you to register a global handler for any unhandled exceptions in your application. Here is the documentation https://docs.microsoft.com/en-us/dotnet/api/system.appdomain.unhandledexception?view=netframework-4.8

TaskScheduler.UnobservedTaskException - I've included this as I'm not familiar with the internals of the framework libraries you are using, but there maybe some asynchronous code happening somewhere, that is potentially not observing the result of a task. If a faulted task (ie an exception was thrown) is never awaited or never has the Result property accessed and then goes out of scope so it can be garbage collected; at some indeterminate point in the future, it will get collected and an UnobservedTaskException will get thrown. Subscribing to this event, will let you handle that scenario. Documentation here

https://docs.microsoft.com/en-us/dotnet/api/system.threading.tasks.taskscheduler.unobservedtaskexception?view=netframework-4.8

Source https://stackoverflow.com/questions/59266083

QUESTION

Autofac Property Injection in already registered service

Asked 2017-Jul-16 at 14:32

I'm using Autofac to DI and MVVM. I have a global service registered as such:

...

ANSWER

Answered 2017-Jul-14 at 17:09

Property Injection does not work out-of-the-box, you need to set up class you want to use property injection in, so

Source https://stackoverflow.com/questions/45065725

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Autofac.Extras.NLog

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: