Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Problems with Exception Management Application Block

Problems with Exception Management Application Block

Scheduled Pinned Locked Moved .NET (Core and Framework)
helpdotnetwindows-adminsecurity
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Andy Hochstetler
    wrote on last edited by
    #1

    I'm having difficulty getting the Microsoft Application Block for Exception Management working. In particular, I'm trying to customize the DefaultPublisher so that it uses a custom log source in the EventLog. Here are some of my constraints, many of which I've overcome. 1) I wanted the assembly deployed to the GAC so that more than one app could share it. 2) My apps are web apps, so I had to deal with security issues regarding getting a custom log source set up. OK, so I created my strong names for the ExceptionManagement and Interfaces assemblies, and got both installed to the GAC. No problem. I used the INSTALLUTIL.EXE to run the custom installer for the ExceptionManagement assembly. So far so good. I manually created the registry key and string value for my log source. Next, I set up the web.config file. Here's the way I had it set up the first time:

    Now when I generated an exception, several were logged using my custom log source, including several that it was unable to find the type for the section handler. Well, I figured out that it was because I had an assembly in the GAC and hadn't fully qualified the names. So I fixed the web.config to be:

    Well, now to the point I'm at now. I get an internal exception that has the following detail. I'm at wits end! Any help would greatly be appreciated!!! Thanks, Andy 1) Exception Information *****************************************

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups