I was passing the IContainer in a service so I read that it is not good to pass this around but instead use it only to the root of the app and pass either IComponentContext or ILifetimeScope . So I am trying to understand which shall I use IComponentContext or ILifetimeScope. Dont understand the difference
Autofac IComponentContext vs ILifetimeScope
8.2k Views Asked by pantonis At
1
There are 1 best solutions below
Related Questions in C#
- Passing arguments to main in C using Eclipse
- kernel module does not print packet info
- error C2016 (C requires that a struct or union has at least one member) and structs typedefs
- Drawing with ncurses, sockets and fork
- How to catch delay-import dll errors (missing dll or symbol) in MinGW(-w64)?
- Configured TTL for A record(s) backing CNAME records
- Allocating memory for pointers inside structures in functions
- Finding articulation point of undirected graph by DFS
- C first fgets() is being skipped while the second runs
- C std library don't appear to be linked in object file
- gcc static library compilation
- How to do a case-insensitive string comparison?
- C programming: Create and write 2D array of files as function
- How to read a file then store to array and then print?
- Function timeouts in C and thread
Related Questions in AUTOFAC
- AutoFac Lifetime scopes for Isolated Azure Functions
- Using Autofac with HostApplicationBuilder
- Autofac: Registering a Singleton and InstancePerDependency Dependency Relationship
- Scoped services via delegate factories in singleton services with autofac
- How to implement Chain of Responsibility design pattern using Autofac
- How to go about catching controller activator exceptions in order to log them?
- ASP.NET Core 6+, Autofac, TreeRouteBuilder costructor not found
- Get a collection of all IOptions objects with autofac
- autofac - Not able to use EnableClassInterceptors with expression registration or lambda registration techniuqe
- How to mock IProcess to in a c# Unit test
- Hangfire & Autofac.Core.Registration.ComponentNotRegisteredException: The requested service has not been registered
- Register assembly types as self and as specific interface
- Autofac Dependency Injection for Azure Table and EntityFrameworkCore InMemoryDb
- webforms IEnumerable property set to empty and reset its value
- Autofac time driven [tagged] scope
Related Questions in AUTOFAC-CONFIGURATION
- What is meaning of `key` in autofac configuration file?
- Adding Autofac JSON configuration to .NET core 6.0 using the new single file template
- Export an autofac container to its identical json configuration file
- How to Resolve ILogger in Autofac container
- Is it possible to make Autofac fail if there are multiple singleinstance-registrations for a single interface?
- AutoFac get multiple instances of same service injected but constructed differently
- Autofac RegisterAssemblyOpenGenericTypes matching query
- Autofac - How to access IRegistrationBuilder from IResolvePipelineBuilder & ResolveRequestContext?
- Implementing IConfiguration with Autofac
- Measure and monitor Autofac resolve time of individual components
- I have installed autoFac and AutoFac.Mvc5 both but RegisterControllers() method is not Available
- Singleton BackgroundService not started by Autofac
- inject module properties to dynamically registered component
- Accesing Application DI Container in Configure Services
- Autofac.Core.DependencyResolutionException: Expression of type '' cannot be used for return type 'System.Object' in Autofac 6.2
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
ILifetimeScope extends IComponentContext. It adds a few methods for beginning new lifetime scopes. If you need to create a new lifetime scope, then take a dependency on
ILifetimeScope, otherwise I would suggestIComponentContext, so that you don't request more functionality than required.Taking a dependency on either one is not an anti-pattern. There is always a boundary between your DI-aware code and the DI-unaware outside world. E.g. Windows has no knowledge about DI, but your code depends on Autofac. On this boundary you need to use
ILifetimeScopeorIComponentContextto bridge this gap. However if you can have your dependencies injected by Autofac instead of retrieved from aIComponentContext, then you should since this is the preferred option.