Reply to: Problem with Enterprise Library Logging Block

[Weltchy]

You could at least put [CODE]...[/CODE] tags around it

I bow my head to the person with greater forum skills than I

[NickFitz]

Have you got the required sections in the configSections block of web.config.

ie.

  <configSections>
    <section name="loggingConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=051e068228f92cd6" />
    <section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null" />

Also, your logging configuration should be something like this

  <!--Added For Event Logging Application Configuration-->
  <loggingConfiguration name="Logging Application Block" tracingEnabled="true" defaultCategory="General" logWarningsWhenNoCategoriesMatch="true">
    <listeners>
      <add source="Enterprise Library Logging" formatter="Text Formatter"
			  log="Application" machineName="" listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.FormattedEventLogTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=051e068228f92cd6"
			  traceOutputOptions="None" type="Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.FormattedEventLogTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=051e068228f92cd6"
			  name="Formatted EventLog TraceListener" />
    </listeners>
    <formatters>
      <add template="Timestamp: {timestamp}&#xD;&#xA;Message: {message}&#xD;&#xA;Category: {category}&#xD;&#xA;Priority: {priority}&#xD;&#xA;EventId: {eventid}&#xD;&#xA;Severity: {severity}&#xD;&#xA;Title:{title}&#xD;&#xA;Machine: {machine}&#xD;&#xA;Application Domain: {appDomain}&#xD;&#xA;Process Id: {processId}&#xD;&#xA;Process Name: {processName}&#xD;&#xA;Win32 Thread Id: {win32ThreadId}&#xD;&#xA;Thread Name: {threadName}&#xD;&#xA;Extended Properties: {dictionary({key} - {value}&#xD;&#xA;)}"
			  type="Microsoft.Practices.EnterpriseLibrary.Logging.Formatters.TextFormatter, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=051e068228f92cd6"
			  name="Text Formatter" />
    </formatters>
    <categorySources>
      <add switchValue="All" name="General">
        <listeners>
          <add name="Formatted EventLog TraceListener" />
        </listeners>
      </add>
    </categorySources>
    <specialSources>
      <allEvents switchValue="All" name="All Events" />
      <notProcessed switchValue="All" name="Unprocessed Category" />
      <errors switchValue="All" name="Logging Errors &amp; Warnings">
        <listeners>
          <add name="Formatted EventLog TraceListener" />
        </listeners>
      </errors>
    </specialSources>
  </loggingConfiguration>

PS - I'm too lazy to reformat the above xml, so its all yours. Also, depending on which version your using, whether you've put the library into the GAC, etc, then the assembly references to the Enterprise Library may also be different

You could at least put [CODE]...[/CODE] tags around it

[Weltchy]

Of course! Do you want to go direct to SY01 or sub-contract via me?

Lets get some sort of circular sub-contractor chain going. I'll bill you, SY01 can bill me. I'm get some cheap as chips indian guy to do all the real work and we can make lots of money!!!

Anyway, back to the real world and writing SharePoint EventHandler code

[voodooflux]

Cough Cough. Don't forget my consultancy fee!!

Of course! Do you want to go direct to SY01 or sub-contract via me?

[Weltchy]

Let me know where to send the invoice

Cough Cough. Don't forget my consultancy fee!!

[voodooflux]

I'll get you resourced into the plan

Let me know where to send the invoice

[suityou01]

This probably doesn't help but I just created a quick WinForms project in Visual Studio 2008 with your config and it worked OK (although I had to add the missing </configuration> closing tag - probably just a cut n' paste omission in your post though).

I'll get you resourced into the plan

[voodooflux]

This probably doesn't help but I just created a quick WinForms project in Visual Studio 2008 with your config and it worked OK (although I had to add the missing </configuration> closing tag - probably just a cut n' paste omission in your post though).

[voodooflux]

Just checking the obvious, but when you created the config file, was it called app.config and what are the compilation options for it? When you build the project, is the config file being renamed to match [Executable].config? I wonder if for some reason the App.Config file is not being picked up?

It's always the obvious that goes wrong.

Checking now, thanks for your help btw.

Based on your previous posts I am correct in guessing that this is a WPF application? If so Weltchy could be on to something there - by default when you add an application config file to a WPF application it appears to be named app1.config rather than app.config, and needs to be renamed.

EDIT: forget all that in light of your last post.

[suityou01]

Just checking the obvious, but when you created the config file, was it called app.config and what are the compilation options for it? When you build the project, is the config file being renamed to match [Executable].config? I wonder if for some reason the App.Config file is not being picked up?

MyApp.exe.config
Build Action = none
It is set to copy to output directory = always

[suityou01]

Just checking the obvious, but when you created the config file, was it called app.config and what are the compilation options for it? When you build the project, is the config file being renamed to match [Executable].config? I wonder if for some reason the App.Config file is not being picked up?

It's always the obvious that goes wrong.

Checking now, thanks for your help btw.

[Weltchy]

Just checking the obvious, but when you created the config file, was it called app.config and what are the compilation options for it? When you build the project, is the config file being renamed to match [Executable].config? I wonder if for some reason the App.Config file is not being picked up?

[suityou01]

Hrm, without trawling deep into my own code, don't you also need to set the category property for the LogEntry object?

The code is lifted from another project and it works. I followed the MSDN article on how to configure EL Logging, and compared each and every node with the project that was working.

As a last resort I posted here.

[DiscoStu]

I'm so disappointed. Looking at the CUK front page, the title of this thread was Problem with Enterprise... I was hoping for a warp core issue or a problem with the photon torpedoes

[Weltchy]

Hrm, without trawling deep into my own code, don't you also need to set the category property for the LogEntry object?