enterprise-library

How can I to get working the Data redirected section for EnterpriseLibrary Data Access Application Block? I would do like to have the definitions for databases removed from app.config and placed on a standalone database.config file. I try to do the same way I am doing with the logging.config and and exception.config files but I can't get it work. using Microsoft.Practices.EnterpriseLibrary.Common.Configuration; using Microsoft.Practices.EnterpriseLibrary.Data; using Microsoft.Practices.EnterpriseLibrary.Data.Sql; using Microsoft.Practices.EnterpriseLibrary.ExceptionHandling; using Microsoft

Enterprise Library Validation Application Block (VAB) integrates with ASP.NET and also with WCF. Is there a way to integrate ValidationResults created in WCF with ASP.NET? e.g. an ASP.NET web page invokes a WCF service. The WCF service validates the data using VAB and returns validation information via a FaultContract. The ASP.NET page can take the results and display some error messages. However, a common approach is to indicate which fields have errors (e.g. inline message or asterisk). It seems that most of these approaches will involve being able to correlate the validation result with a

For the life of me I can not find the Enterprise Library Strong Naming Guidance Package download for Enterprise Library 4.1 I need this to sign the assemblies to add them to the GAC. Does anybody know where I can find it? I can't find it anywhere on the www.codeplex.com/entlib or www.codeplex.com/entlibcontrib websites. HELP! According to this , the shipped binaries are already strong named, so you should be good to go . EDIT: If you modified the source, use this guide . The guidance package was checked in to EntLibContrib: http://entlibcontrib.codeplex.com/SourceControl

I've found a very good article about how to use EntLib Validation Block for server validation in MVC 2. But as there pointed out The current design of EntLib’s Validation Application Block uses the Composite pattern; that is, when we ask for validation for an object, it returns back a single validator object that contains a list of all the validation work to be done. While this is very convenient from a normal usage scenario, the unfortunate side-effect is that we can’t “peek inside” to see what the individual validations are that it’s doing, and therefore can’t generate the appropriate client

Can anyone clarify if Enterprise Library's Database object can be made static without any thread-safety issues? Yes, an Database instance is thread-safe. It is just a big factory spitting out new objects like connections. The instance itself doesn't change state after it is created. When you look at the source code you can see this clearly. The objects it produces are of course not thread-safe. You can, but there's no significant reason to. Database instances are cheap to create and don't hold any state. No don't do it. I tried it and was sorry that I did. While it was thread safe it slowed