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
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
We write MS Office add-in. These should start fast beacause Office should start fast. We use EntLib. We found that configuration takes time to start. I hope for faster to start version of configuration for desktop. Details are here http://asdandrizzo-se.blogspot.com/2013/06/issues-using-entlib-and-unity.html12 votes
Allow CData parameters to help with registering for example dictionary like types
<register type="IValueProcessor" name="AbbreviationProcessor" mapTo="KeywordValueProcessor">
<lifetime type="singleton" />
<param name="replacements" type="DictionaryStringString">
Will EnterpriseLibrary.Config support Visual Studio 2012 ? http://visualstudiogallery.msdn.microsoft.com/029292f0-6e66-424f-8381-3454c8222f91 vote
- Don't see your idea?