Consider providing a IDatabase interface to for example make mocking of database dependency much easy.

Will EnterpriseLibrary.Config support Visual Studio 2012 ? http://visualstudiogallery.msdn.microsoft.com/029292f0-6e66-424f-8381-3454c8222f9

It would be nice to have write extension for Visual Studio providing in configuration file Intellisense. It should show types referenced by assembly that can be registered in container.

Optional<T> is a constructor parameter which is not an essential dependency of a class but can be needed for some actions. This is very helpfull if you have for example licence features in your application. You can than register on startup only components which are licensed and your other components can decide which parts to show or use based on the available features. Like nullable types it needs a HasValue or IsRegistred property to check if a type can be instanciated.
IEnumerable<T> is needed to get all registrations of a particular type.

Shorter names are better if no meaning is lost. Let consider Microsoft.Practices.EnterpriseLibrary.Logging.dll and Microsoft.Practices.Enterprise.Logging.dll. We all now that Enterprise is Library via dll extension. So VS problem of long paths and hurt of devs without ReSharper will be less, and without lost of meaning.

It would be great and nice to include the Resource Application Block by providing more and easy features to Extending the ASP.NET 2.0 Resource-Provider Model.

http://msdn.microsoft.com/en-us/library/aa905797.aspx

Hello,
ITransientErrorDetection.IsTransient accepts only an exception and it forces the code to throw exceptions even if not needed. I think it would help having an additional interface defined with a generic type, for example

public interface ITransientErrorDetection<T>
{
bool IsTransient(T error);
}

This way it would still work with the current implementation of retry policy, but also allow cases when the error is not an exception but an error code or message. An example of usage would be with HttpClient which doesn't throw an exception when a return status code is an error

Thoughts?

Thanks,
Pedro

Add support for spatial data in SQL 2008+. DbType must support geography and geometry types. Right now I have to convert those data to string and pass as parameters. Please add support for Szstem.Data.Spatial namespace datatypes and other spatial helper methods.

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.

All components should configuration elements if used with Windows Azure.

For example, I should be able to log to blob or security block should be able to interface with WIF

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.

When installing Enterprise Library 5 Configuration Tool you get 4 different executables:
- EntLib Config .NET 3.5 (x86)
- EntLib Config .NET 3.5
- EntLib Config .NET 4 (x86)
- EntLib Config .NET 4

I think that the Configuration Tool should be only one for simplicity if possible and that target framework version could be included in the configuration XML if needed.

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.Win8

See:

http://unity.codeplex.com/discussions/400636#post931911

Details are available in the discussion thread -

http://entlib.codeplex.com/discussions/395334

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.

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.

don't know how but is it possible to add interception support for async/await methods?