.Net defines a "Trace Source" concept, allowing configuration files to specify which trace sources to listen for messages on. WCF provides several trace sources, and I would presume that other portions of the .Net Framework BCL publish other trace sources as well. What is the list of trace source names published to by the BCL?
Some More (includes Hans answer):
- CardSpace
- Microsoft.Transactions.Bridge
- System.Activities
- System.Activities.Core.Presentation
- System.Activities.DurableInstancing
- System.Activities.Presentation
- System.ComponentModel.Composition
- System.IdentityModel
- System.IO.Log
- System.Net
- System.Net.Cache
- System.Net.Http
- System.Net.HttpListener
- System.Net.Sockets
- System.Net.WebSockets
- System.Runtime
- System.Runtime.Serialization
- System.Runtime.Serialization.CodeGeneration
- System.Security.Cryptography.Xml.SignedXml
- System.ServiceModel
- System.ServiceModel.Activation
- System.ServiceModel.MessageLogging
- System.ServiceModel.OperationInvoker.CodeGeneration
- System.ServiceModel.Routing
- System.Transactions
- System.Web.Services.Asmx
- System.Windows.Data
- System.Windows.DependencyProperty
- System.Windows.Documents
- System.Windows.Freezable
- System.Windows.Interop.HwndHost
- System.Windows.Markup
- System.Windows.Media.Animation
- System.Windows.NameScope
- System.Windows.ResourceDictionary
- System.Windows.RoutedEvent
- System.Windows.Shell
- System.Workflow.Activities
- System.Workflow.Activities.Rules
- System.Xaml.Hosting
Menu
979
answered Sep 27 '22 21:09
