Enterprise Library / Unity vNext
Greetings!
This is a public forum for you to suggest/vote on the ideas for future capabilities/updates to Enterprise Library and Unity.
Please note the list may not always represent the actual prioritized backlog of the development team.
3 results found
-
add bulk updates in the Database Logging Tracelistener
The database TraceListener is great for logging up to a certain point, but beyond that it runs out of capacity somewhat. If one was able to send updates in batches to the logging database instead of having to call the stored procedure line by line I think it would increase throughput considerably for relatively little effort.
4 votes -
Defaults for Configuration
Configuring EntLib is still very verbose. The config builders allow you to provide meaningful default values for many cases. E.g. logging could be done by something like
var builder = new ConfigurationSourceBuilder(...);
builder.ConfigureLogging();which will setup rolling file logging to a file named default.log with the default message formatter etc.
26 votes -
Add support for all the Autofac Relationship types
In this article: http://nblumhardt.com/2010/01/the-relationship-zoo/, Nicholas Blumhardt talks about relationship types supported by Autofac. Othe IoC containers have supported some if not all of these over the years, Unity needs to catch up.
The Lazy<T> and the Owned<T> relationship type are the most interesting from a what's currently missing point of view.
32 votes
- Don't see your idea?