March 2006 - Posts

After Colin released Avanade's "Integration Pack for Microsoft Enterprise Library" on his avablog, I cooked you guys a version of the Enterprise Library Extensions that works within this integration pack.

All of the features: Envrionmental Overrides, Configuration Protector and Configuration Constants writer are now available from within Visual Studio 2005.

As a small bonus in this release I also added another configuration node that manages the appSettings section of your configuration file (can be used from within Visual Studio or the Configuration console).


(Managing appSettings from within Visual Studio)


Please note: There could be some minor glitches when editing appSettings from within Visual Studio, the focus within the propertygrid is lost after editing a "Key" property.
Colin told me he'll look into this for his next release.

Installation and download
Please visit the Enterprise Library Extensions page for the latest download and installation notes

Colin has been doing an excelent job integrating Enterprise Library into Visual Studio and expects to have an installer released in the public later this week.

ELIP 
Would you really want to stick with the standalone solution? I wouldn't.

Environmental Overrides
The ‘Environmental Overrides’ extension is back and works with Enterprise Library 2.0.




Functionally not much has changed; therefore I refer to this
explanation on the usage of the extension and a couple of example usage scenarios.
This drop contains the complete set of extensions for Enterprise Library v.2 of which some are changed and bugs are fixed. Make sure you update all all the extensions after downloading.

Installation and download
Edit: Please visit the Enterprise Library Extensions page for the latest download and installation notes



Is there more?
Next up would be the ‘Naked ConfigurationNode’ which should make it extremely easy to add designtime support to any .NET 2.0 configuration structure.
I’m currently developing it and making an implementation against System.Web’s configuration (that will hopefully prove my point ;-)).