How many custom EventSource classes with SLAB?

Topics: Semantic Logging Application Block
Aug 16, 2013 at 2:50 PM
What is the recommended practice using the SLAB on a multi-assembly solution? Should I generally have one EventSource per assembly? It seems I would need to in order to capture strongly typed data. The samples I've seen usually have a single project and don't cover this scenario.
Aug 19, 2013 at 8:42 PM
I don't think there is any specific recommendation for all scenarios. As in most design considerations it depends. I can imagine a scenario where there is one assembly that contains contains multiple EventSources across an organization. Or perhaps more likely, each application has one or more EventSources defined in a shared, common assembly. Or maybe each functional area has it's own EventSource? You also might have break it out across different assemblies depending on the target environment (e.g. client vs. server).
Should I generally have one EventSource per assembly?
I don't think that is true as a general statement but you could definitely implement it that way.

Randy Levy
Enterprise Library support engineer
Support How-to