UAB fails with latest EnterpriseLibrary assemblies

Topics: Updater Application Block
Feb 9, 2005 at 7:56 AM
originally posted by: dlm451

Is anyone using assemblies built from the downloaded Enterprise Library with the
Updater Application Block?

I downloaded the Enterprise Library, built the assemblies, and thought I could use those
built assemblies to step through the source on methods used by the Updater Application Block--
instead of the EntpriseLibrary assemblies which come in the \Common directory.

It looks like the Enterprise.Configuration assembly that comes with Updater Application Block
is built from a different source base than the current downloaded Enterprise Library Application

For example:
The Microsoft.Practices.EnterpriseLibrary.Configuration.Dll that's in the \Common directory
of the UAB contains the class ConfigurationCursor and the class ConfigurationManager
has the methods GetConfig() and WriteConfig().

The Microsoft.Practices.EnterpriseLibrary.Configuration.dll built from the downloaded
Enterprise Library from Patterns and practices does not contain the
class ConfigurationCursor, and the class ConfigurationManager's methods have
changed from GetConfig() to GetConfiguration() and WriteConfig() to WriteConfiguration().

Maybe I downloaded the wrong bits? Or is the UAB out of sync with the EnterpriseLibraries?

This is the assembly that comes with the UAB download:

// Assembly Microsoft.Practices.EnterpriseLibrary.Configuration, Version

Location: C:\Apps\Windows Updater Application Block

Name: Microsoft.Practices.EnterpriseLibrary.Configuration, Version=, Culture=neutral,


This assembly contains ConfigurationCursor
This Assembly contains ConfigurationManager.GetConfig and WriteConfig()

This is the assembly built from the Enterprise Library download:

// Assembly Microsoft.Practices.EnterpriseLibrary.Configuration, Version

Location: C:\Program Files\Microsoft Enterprise

Name: Microsoft.Practices.EnterpriseLibrary.Configuration, Version=, Culture=neutral,


This assembly does not contain ConfigurationCursor
ConfigurationManager.GetCongfiguration() and WriteConfiguration()
Feb 9, 2005 at 11:02 AM
originally posted by: jcelich

That's because the drop you have for UAB was built with an earlier version of EntLib, not the last January drop.
Next UAB drop will include those new bits of EntLib.