Tracing mechanism in Windows Communication Foundation is based on the
classes that resides in System.Diagnostic namespace.Important classes are Trace,
TraceSource and TraceListener.
Following are the steps to enable tracing
in WCF:
1. Configuring WCF to emit tracing information/Define Trace Source,
we have the following options:
System.ServiceModel
System.ServiceModel.MessageLogging
System.ServiceModel.IdentityModel
System.ServiceModel.Activation
System.Runtime.Serialization
System.IO.Log
Cardspace
In configuration file, we will define a source to
enable this configuration as follows:
2. Setting Tracing Level, we have the
following available options, we need to set this tracing level to available
options other than default "Off":
Off
Critical
Error
Warning
Information
Verbose
ActivityTracing
All
In configuration file, we can choose above
values for switchValue attribute as follows:
switchValue=”Information”>
3. Configuring a trace listener
For configuring a trace listener, we will add
following to config file.
type="System.Diagnostics.XmlWriterTraceListener"
initializeData="d:\logs\messages.svclog"
/>
logEntireMessage: By default,
only the message header is logged but if we set it to true, entire message
including message header as well as body will be
logged. logMalformedMessages: this option log messages those
are rejected by WCF stack at any stage are known as malformed
messages. logMessagesAtServiceLevel: messages those are about
to enter or leave user code. logMessagesAtTransportLevel:
messages those are about to encode or decode. maxMessagesToLog:
maximum quota for messages. Default value is
10000. maxSizeOfMessageToLog: message size in bytes.
Putting all this together, configuration file
will appear like this.
Note: In this case, information will be
buffered and not published to file automatically, So, we can set the autoflush
property of the trace under sources as follows:
example of creating a simple Task Dashboard. This is a pretty basic example of using all OOTB (out of the box) features and combining them to quickly build a solution. Scenario: We want to provide a way for users to easily see a summary of the current project tasks. We want them to be able to see the following information: Open Tasks Assigned to Them Overdue Tasks Tasks Due This Week Task Calendar Tasks Assigned to Others Solution: To build this solution we will be using several different tools available in SharePoint, all included in the list below: Task List Task List Views We will create views for each of the different ways we want to see the data displayed on our dashboard. Web Part Page List View Web Parts Custom Navigation The first thing we will do is create our task lists and then configure all the views that we need. To create the list, go to View All Site Content, Create and then select the Task list. Next, we will need to configure our custom views. To do this, w
In this post we are gonna discuss about MERGE transformation. MERGE in SSIS is equal to UNION ALL in SQL Server. This transformation unions two datasets/tables.The merge Transformation combines two sorted dataset into single dataset. Highlighted the text SORTED in last statement because “It is not possible to use MERGE when the inputs are NOT SORTED”. There is one more transformation which is very similar to this i.e UNION ALL. The Merge Transformation is similar to the union all transformations. Use the union all transformation instead of the merge transformation in the following situations. The transformation inputs are not sorted The combined output does not need to be sorted. The transformation has more than two inputs. MERGE takes ONLY TWO inputs where as UNION ALL can take more than two. Now lets see how to configure MERGE transformation with an example. I created TWO tables with names MergeA and MergeB and inserted few records into each table as shown below.
Comments