Config tool loads DAAB by default

Topics: Data Access Application Block, Enterprise Library Core, Pre-release discussions
Jan 31, 2007 at 6:17 PM
Something has been intriguing to me for a while now. Whenever I load an empty app.config in the EntLib Config tool (now integrated into VS.NET 2005 with CTP Jan 2007 of entlib v3), it is as though I have a DAAB configured already. When I look at the actual XML, there is no mention of DAAB. So why would the config tool load a DAAB in the config by default, without me explicitely adding it to my application?

Is it a bug? Is it to reduce the developer's amount of work to do to set app blocks? It just doesn't make much sense to me. It's actually causing some fuss (design-time "compiling errors" in the integrated config tool) when i already have some settings in the file before opening it with the config tool.

Please, enlighten me.

Jan 31, 2007 at 7:40 PM
This behavior is described here. The short answer is that the DAAB shows up since machine.config includes a <connectionString> declaration by default which is available to every application.