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.
5 results found
-
Unity configuration tool
Add a graphical config tool for Unity like it already exists for the other app blocks
114 votesdeclined · AdminGrigori Melnik (Producer) (Senior Program Manager, Microsoft Enterprise Library) respondedSpiked on this and concluded that config tool would not adequately address the story. On the contrary, complicated visual graphs would only confuse things. I’d like to encourage voters for this story to submit new stories describing concrete scenarios where they felt a config tool might help. We’ll review those and see how we tackle them in vNext.
-
Change the Secuirty Block to be a wrapper for Claims Identities
A general wrapper to handle claims tokens and WIF, Azure ACL oAuth, SWT, etc. It should be a pluggable module so others can provide a pluggin for other Token systems.
36 votesdeclined · AdminGrigori Melnik (Producer) (Senior Program Manager, Microsoft Enterprise Library) respondedSecurity Application Block is being depecated.
-
EF using DAAB
I would like to make the Entity Framework SQL result be executed through DAAB, using its classes to persist and retrieve data from database
18 votesdeclined · AdminGrigori Melnik (Producer) (Senior Program Manager, Microsoft Enterprise Library) respondedCan you provide a concrete scenario and how DAAB can add value?
-
Wrap DAAB Around Entity Framework
Wouldn't it be great if the DAAB wrapped Entity Framework with these patterns out of the box: Repository / Unit of Work / Specifications / Request-Response, and some form of facading / service layer construction all held together by Unity. How awesome would that be? I could get on with interesting stuff rather than all this tedious wiring up.
6 votes -
Continue to Support .NET 4.0/Windows 7/Windows Server 2008
You say
"The way we envision Enterprise Library v6.0 and Unity 3.0 is that they will be targeted at Windows 8 and Windows Server 2012 developers that are using .NET framework 4.5."
I hope this does not mean that you will remove support for .NET 4.0. Please clarify either way.
2 votesdeclined · AdminGrigori Melnik (Producer) (Senior Program Manager, Microsoft Enterprise Library) respondedEntLib6 and Unity3 rely on the .NET framework features which were introduced in v4.5. For example, the new Semantic Logging Application Block builds on top of the System.Diagnostics.Tracing.EventSource for production logging, while Unity3 uses the new Reflection API.
- Don't see your idea?