Skip to content

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

65 results found

  1. Add Static Factory Support to Stand-Alone Interception

    When using stand-alone interception, ability to use a static factory method for instance creation would be nice.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Interception  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Extension Hooks similar to WebActivator

    WebActivator is a great conventions for embedding hooks that get wired up in the assembly. The basic idea would be to allow for a static method in an assembly that would take a single IUnityContainer parameter and allow the developer to embed and extension/setup logic in there. This would help with NuGet packages that want to register items by default without configuration manipulation.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unity  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Enhance Performance of the IsRegistered Check on Type Registrations for Unity

    This would allow for more performant resolution of multiple dependency resolvers. See using Unity with SignalR for an example, or this discussion on Unity's Codeplex site - http://unity.codeplex.com/discussions/392550

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Unity  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. ActivationException occurs when resolving LogWriter from container

    The bug http://entlib.codeplex.com/workitem/32970 tracks the problem.

    The discussion where I posted the problem is available at - http://entlib.codeplex.com/discussions/389044

    This results in reliability issues in our production code. Hence it should be an important issue to fix IMHO.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Logging  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow intercept everithing when interact with the database from creating connection to executing SQL and adding parameter

    I would like to have a way to intercept everything inside DAAB. For example, I would like to intercept before execute SQL to set the context_info

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Access  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow custom default LifetimeManagers

    One of the things I like most about Unity, is that Unity can build object trees, even if not all types used in the object tree are explicitly registered.
    However, if I want to use a custom default LifetimeManager, I do have to register all types with the custom LifetimeManager, because Unity does not support a custom default LifetimeManager.
    So, the request is simple: make the default LifetimeManager type configurable.

    E.g.:
    var container = new UnityContainer();
    container.ChangeDefaultLifetimeManagerTo<ContainerControlledLifetimeManager>();

    105 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Entlib Logging for HTML 5 Applications

    In ASP.MVC 4 there's a Template that generates Single Page Applications in Browser. Much more code is running in the browser runtime and the need for Tracing and ErrorLogging is higher in these scenarios. Are there any plans to support HTML 5 Applications that are built with the Single Page Pattern?

    I would like wish to see a similar support that has been built for Silverlight. Especially a centralized LoggingServices that supports ASP.NET, MVC and WCF and accepts JSON LogEntries. A client side javascript library and configuration would help to generate these messages via ajax and send them asynchronously. I…

    107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Allow CData elements to help with Dictionary registration

    Allow CData parameters to help with registering for example dictionary like types

    <register type="IValueProcessor" name="AbbreviationProcessor" mapTo="KeywordValueProcessor">
    <lifetime type="singleton" />
    <constructor>
    <param name="replacements" type="DictionaryStringString">
    <cdata typeConverter="PipeStringToDictionaryStringStringTypeConverter">
    <![CDATA[
    ACCEPTANCE|ACPT.
    ACCESSORIES|ACCES.
    ACCOMMODATION|ACCOM.
    ACCOMMODATIONS|ACCOMS.
    ]]>
    </cdata>
    </param>
    </constructor>
    </register>

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Configuration  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Support a Rolling Database Trace Listener

    The Database Trace Listener and the supplied stored procedure are not really helpful over time. The database is growing indefinetly. It would be cool to have a similar mechanism as the rolling file listener.
    The database can specify how large it can grow maximum and old entries are deleted automatically.

    61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Register multiple instances without naming them

    And then resolve all these instances by ResolveAll

    50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. One assembly for referencing

    Now to reference Unity I need to reference 3 asms: Unity/Unity.Configuration/System.Configuration. Change it to only 1, please. When I'm allways trying that my component user feel comfortable to reference only one "business logic" assembler, I should instruct them also to reference three additional dlls...

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Improve XML configuration

    Make Unity to be fully configurable with XML file.
    Add support for
    1) Factory methods and abstract factories;
    2) Macros;
    3) Building configuration from several files at the same time.

    Make XML config file syntax more concise and Source-Control friendly.

    80 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. wcf service factory

    Exposing a unity-managed object with wcf through a svc file is a common scenario. It would be great if Unity could provide a wcf factory out of the box, so it would be possible to use it directly instead of writing our own (many examples on the web).

    147 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Shorter xml syntax for initializing objects

    Initialize properties in one configuration string <parameter="loggingOptions" macro="Debug=true; Trace=false;"/>

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Nested Configuration

    it would be great to register nested objects instead of using dendencyName. This way the xml, will reflect the object tree visually.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Provide include semantics for config

    I would like to extract alias definitions to a centralized config file and reference this from the master app config. See:
    http://stackoverflow.com/questions/7848139/is-it-possible-to-move-the-container-alias-definitions-into-a-separate-file

    38 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Facilities

    Castle Windsor Facilities equivalent

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Use claims for authorization checks

    As a developer I want to be able to leverage a ClaimsPrincipal for the authorization checks using the Security Application Block. The claims that are recognized as identity or roles should tie into the authorization providers (AuthorizationRuleProvider and AzManAuthorizationProvider). Currently the AzMan provider seems dependent on Windows identities.

    107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Enterprise Library / Unity vNext

Categories

Feedback and Knowledge Base