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.
65 results found
-
'Topaz' for 'Service Bus for Windows Server'
I would recomend to add support of 'Topaz' for 'Service Bus for Windows Server'. It should be fairly easy to do because 'Service Bus for Windows Server' and 'Azure Service Bus' have a common codebase.
29 votes -
Same handlingInstanceID when an exception was already handled by the block
Exception Handling Application Block
It would be very useful if an exception that was already handled by the block uses the same handlingInstanceID generated the first time it was handled so you can associate all the exception chain as only one error.
If the exception was already handled the block uses the same handlingInstanceId generated before, if not then it generates a new one.
e.g. Supose that you show the handlingInstanceId to the user as a ticket number of the error. You want to track down what happen using that ticket number, but if your model handles the exceptions in…
9 votes -
Rapid integration with popular Microsoft Frameworks / Bootstrapper
Rapid integration with popular Microsoft Frameworks. For example:
Install-Package Unity.Mvc
- I don’t have to write a single line of code and my MVC will now use Unity
And so on…
Install-Package Unity.Http
Install-Package Unity.Wcf
Install-Package Unity.Win866 votes -
5 votes
-
RollingFileTraceListener generates filenames with GUIDs
Details are available in the discussion thread -
4 votes -
RollingFileTraceListener should have option to put column headers
Using the RollingFileTraceListener we write a CSV file (in our production environment).
It would be useful for us if the CSV files had column headers. This option is not available I believe in the current framework.
4 votes -
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 -
interception on async/await methods
don't know how but is it possible to add interception support for async/await methods?
34 votes -
Please use the Portable Class Library (PCL) for the next release
Using the portable class library we will be able to easily reuse our core classes in multiple platforms.
56 votesunder review ·
AdminGrigori Melnik (Producer)
(Senior Program Manager, Microsoft Enterprise Library)
responded
Please see my comments on the story.
-
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 assembly and namespace like unity to other blocks, mainly logging and exception handling
Currently the config file is too verbose because the namespaces of the entlib blocks are very large. One way to solve this would be to register the assembly, similar to the unity schema.
15 votes -
Avoid needing to create a new ExceptionFormatter for a custom format.
Log exception using the log formatter of the logging category or define one inline.
3 votes -
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 -
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 -
Add transitory failure & retry logic for SQL 2012 AlwaysOn support
Add transitory failure and retry logic for SQL 2012 AlwaysOn support to the data application block
11 votes -
Give for generated assembly wellknow names
I want intercept internal types, but now I got error.
Can you make as FakeItEasy https://github.com/FakeItEasy/FakeItEasy/wiki/A-guide-for-faking-internal-(Friend)-types?9 votes -
Custom handling of unresolved types during LoadConfiguration()
I have large hierarchy of objects spread across several assemblies and deployment packages. I want to configure it once and reuse the same configuration file in several applications. I am looking for a way to instruct unity to ignore unresolved <register type=""> entry and continue registering other types.
For my case it would be sufficient just to ignore such types, but ideally this should be an event or callback delegate that would be called on each such event so that it could be handled appropriately.
12 votes -
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 -
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 -
Registration by Assembly Scanning
- Create a basic attribute called "RegisterType" that you could place on a class, The options I've found most useful are an enum to define it's lifetime manager and addtional type attributes to filter out types you don't want to register, IDisposable etc.
- Create an optional attribute that can be put in the assembly to indicate it should be scanned. This is optional but can be helpful for performance reasons.
- Create a Unity extension that reads all loaded types (I've found tricks for web applications here) and scans for this attribute and registers matching types.
50 votes
- Don't see your idea?