EnterpriseLibrary.Logging

[Andrew]

Hi all,

I have installed EnterpriseLibrary v3.1 (latest version) on my pc. When I
create the app.config file using the "EnterpriseLibrary Configuration"
utility, I get an error saying it can't detect the EL.Logging.dll file. I
fixed the problem by setting the PublicKeyToken= "null" instead of its
default PublicKeyToken="b03f5f7f11d50a3a".

eg.
configSections>
<section name="loggingConfiguration"
type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings,
Microsoft.Practices.EnterpriseLibrary.Logging, Version=3.1.0.0,
Culture=neutral, PublicKeyToken=null" />
<section name="exceptionHandling"
type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Configuration.ExceptionHandlingSettings,
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=3.1.0.0,
Culture=neutral, PublicKeyToken=null" />
</configSections>

The thing is that I can't understnad why this error is occuring in the first
place. This pc is newly set-up and it has never had any prior versions of EL
installed on it. The "EnterpriseLibrary Configuration" utility comes with
this v3.1 setup.

Thanks for your reply.

regards,
Andrew

 

[John Saunders [MVP]]

Hi all,

I have installed EnterpriseLibrary v3.1 (latest version) on my pc. When I
create the app.config file using the "EnterpriseLibrary Configuration"
utility, I get an error saying it can't detect the EL.Logging.dll file. I
fixed the problem by setting the PublicKeyToken= "null" instead of its
default PublicKeyToken="b03f5f7f11d50a3a".

eg.
configSections>
<section name="loggingConfiguration"
type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings,
Microsoft.Practices.EnterpriseLibrary.Logging, Version=3.1.0.0,
Culture=neutral, PublicKeyToken=null" />
<section name="exceptionHandling"
type="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Configuration.ExceptionHandlingSettings,
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=3.1.0.0,
Culture=neutral, PublicKeyToken=null" />
</configSections>

The thing is that I can't understnad why this error is occuring in the
first
place. This pc is newly set-up and it has never had any prior versions of
EL
installed on it. The "EnterpriseLibrary Configuration" utility comes with
this v3.1 setup.

Thanks for your reply.

regards,
Andrew

 

[John Saunders [MVP]]

Hi all,

I have installed EnterpriseLibrary v3.1 (latest version) on my pc. When I
create the app.config file using the "EnterpriseLibrary Configuration"
utility, I get an error saying it can't detect the EL.Logging.dll file. I
fixed the problem by setting the PublicKeyToken= "null" instead of its
default PublicKeyToken="b03f5f7f11d50a3a".

You should probably ask this on the Enterprise Library discussions area at
http://www.codeplex.com/entlib/Thread/List.aspx.

 

[Andrew]

Thanks for your suggestion. I have done that.

The problem with posting on that website is that it's kinda difficult to get
a reply to my questions. They are probably too buzy to reply to questions.

cheers
Andrew

 

[sloan]

This is going to sound weird, but try this experiment.


Go here:

C:\Program Files\Microsoft Enterprise Library 3.1 - May 2007\Bin\

ZIP all the dll files.
(so you have a backup)
Delete all the dll files in that directory.
Reboot.
and try you stuff again.

.........

I had a weirdo issue like this...and my zip/bin experiment addressed it.
I never figured out why.

There was some weird mojo going on with the GAC and those \bin\ dlls being
around at the same time.

Yeah, I know..it sounds weird. I wasn't able to build a release version for
2 days until I did that.

...

PLEASE POST if you try it and what happens.
I'm curious to see if it was just me.

 

[Andrew]

I've tried out your method. It's not working for me.

Let me recap what I have done.
zip all the dll files in the C:\Program Files\Microsoft Enterprise Library
3.1 - May 2007\Bin directory
delete all the files in that directory
reboot
unzip the files
try again....

In my application I actually reference the EnterpriseLibrary dlls from the
working copy (c:\EntLib3Src\.... path). This was created during installation
of EL itself where I was prompted to "Extract working copy ..." and "Build
Application Blocks". So perhaps I should delete the files from this directory
instead. I've tried the above method, not working.

Error Message:
Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging
An error occurred creating the configuration section handler for
exceptionHandling
Could not load file or assembly
'Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging

Microsoft.Practices.EnterpriseLibrary.Logging
An error occurred creating the configuration section handler for
loggingConfiguration
Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Logging

Again I can solve the problem by changing the
PublicKeyToken=b03f5f7f11d50a3a'to null or by deleting the PublicKeyToken.
Any other suggestions ?

Thanks
Andrew

 

[Andrew]

OK,

I've solved the problem by changing the paths of my reference to the dll's
in the ProgramFiles directory instead of from the "Working Library Source
Folder" at C:\EntLib3Src\

What is the WLS folder for anyway then ?

thanks
Andrew

 

[sloan]

You weren't supposed to unzip them after reboot.

Aka, you're effectively removing them (even though you got an exact backup)

But if you figured it out..that's good enough.

...

"Working Library Source
Folder" at C:\EntLib3Src\

I don't know exactly, it may be a RELATIVE reference for the demo's. I'm
not sure.

 

[Andrew]

Note:
http://blogs.msdn.com/tomholl/archi...ncompatible-copies-of-enterprise-library.aspx

cheers