Comments (13)
From [email protected] on November 18, 2007 00:13:14
Add property injection to that list.
from autofac.
From [email protected] on December 03, 2007 13:50:26
Add parameterisation/properties for registered modules. Modules should be the primary
focus for XML configuration as they better encapsulate the implementation of the
application c.f. components.
from autofac.
From [email protected] on December 15, 2007 21:09:15
Done, all that remains is to support constructor selection.
from autofac.
From [email protected] on December 16, 2007 02:27:12
What will make a good syntax for this? Keen to avoid confusion with ...
Thinking:
Status: Started
from autofac.
From [email protected] on December 31, 2007 21:25:32
Summary: Add Explicit Constructor Selection to XML Configuration API
from autofac.
From [email protected] on January 02, 2008 23:39:41
Labels: Milestone-Patch
from autofac.
From [email protected] on January 12, 2008 02:00:05
needs to be used to specify an empty, explicit constructor.
from autofac.
From [email protected] on January 12, 2008 03:41:26
Using attributes to interface to the .NET configuration system is underpowered, it
seems.
It regards the absence of a element identically to an empty one. No
luck. It also regards two elements with the same type as the same and
merges them, forcing us to add a unique key like 'position'.
This isn't very likely to get used in practice, so I won't rush in and hack up an
atrocity like:
Will leave this for a future milestone, it might be worthwhile to consider a raw XML
implementation for config.
Labels: -Milestone-Patch Milestone-Release2.0
from autofac.
From [email protected] on January 13, 2008 02:02:47
Status: Accepted
from autofac.
From [email protected] on March 16, 2008 00:45:52
Labels: -Milestone-Release2.0 Milestone-Release1.2
from autofac.
From [email protected] on May 19, 2008 17:05:43
Removed milestone - re-evaluation for inclusion in a later release.
Labels: -Milestone-Release1.2
from autofac.
From [email protected] on June 13, 2008 23:35:09
Labels: Milestone-Release2.0
from autofac.
From [email protected] on August 03, 2009 19:22:51
No requests or action on this, closing.
Status: WontFix
from autofac.
Related Issues (20)
- Instantiated services not disposed on exception during IStartable HOT 1
- Service is not register in Eureka because of Autofac HOT 4
- Trouble with Autofac Container Disposal when Resolving Dependencies in Another Method/Class HOT 7
- ```Scope.TryResolve(FactoryTypes, out var Instance)``` throws HOT 1
- [Xamarin.iOS] Application crashes during apple review process HOT 1
- AttributedMetadataModule slows down service resolution considerably HOT 1
- Type equivalence for the embedded interop types not working HOT 1
- Decorators does not follow ExternallyOwned - problem with lifetime scope on decorator with `IDisposable` implementation
- Are the container and the root lifetime scope different objects after the first child lifetime scope begins? HOT 2
- Add option to fail on ambiguous service resolution HOT 3
- Required properties not working with WebAPI controllers HOT 6
- Configure Autofac so that it's ExternallyOwned for default, and "InternallyOwned" for separate services HOT 1
- Collection Expressions-y Injections HOT 7
- Startable Singleton instantiated twice HOT 1
- AutoFac WebForms object[] problem HOT 5
- Resolutions with many TypedParameter of the same type HOT 2
- ComponentNotRegisteredException thrown when using NUnit Console Runner HOT 1
- Can Autofac Dispose queue cause buffer overflow or heap corruption? HOT 1
- Register service with Interceptor, then register multiple decorator, auto apply Interceptor to the outermost decorator HOT 13
- Attempt by security transparent method 'Autofac.Integration.Mvc.RegistrationExtensions.RegisterControllers(Autofac.ContainerBuilder, System.Reflection.Assembly[])' to access security critical type 'Autofac.Builder.IRegistrationBuilder`3<System.Object,Autofac.Features.Scanning.ScanningActivatorData,Autofac.Builder.DynamicRegistrationStyle>' failed. Assembly 'Autofac.Integration.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=17863af14b0044da' is marked with the AllowPartiallyTrustedCallersAttribute, and uses the level 2 security transparency model. Level 2 transparency causes all methods in AllowPartiallyTrustedCallers assemblies to become security transparent by default, which may be the cause of this exception. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autofac.