Clog: Client Logging for .NET

New Post: How to use Clog Silverlight in my project?

danielvaughan — Sat, 22 Nov 2008 11:18:46 GMT

That's right.

New Post: How to use Clog Silverlight in my project?

renshao — Sat, 22 Nov 2008 11:10:02 GMT

Hi Daniel,
Thanks for the quick reply. So, if I'm right, I still have to create a service on server-side, called ClogService.svc, and the content of this file would be:
<%@ ServiceHost Language="C#" Debug="true" Service="Orpius.Logging.ClogService" %>

Then I have to edit Web.config in the same way as it did in ExampleSilverlightProject ?

is that right?

New Post: How to use Clog Silverlight in my project?

danielvaughan — Sat, 22 Nov 2008 11:02:29 GMT

Hi Renshao,

The CodeBehind attribute is only used by Visual Studio. You don't need it, and it can be safely removed.
That's right, you don't need to reference ClogService.svc.cs. You will, however, need to make the Orpius.Logging assembly, and a LogStrategy assembly (e.g. Log4NetLogStrategy) available to you web application. You can do this by adding a Reference to them.

Cheers,
Daniel

New Post: How to use Clog Silverlight in my project?

renshao — Sat, 22 Nov 2008 10:40:43 GMT

I don't know how to use Clog. Could anyone briefly explain how to use Clog in your Silverlight project?

Well, at this stage, the only way I can get it work is to port my existing code to the "ExampleSilverlightProject" I downloaded. But how do I use it in my project? I try to configure my Web.config the same way as the sample project but I have one problem: in ClogService.svc, there's
<%@ ServiceHost Language="C#" Debug="true" Service="Orpius.Logging.ClogService" CodeBehind="../../../Clog/Source/Logging/ClientService/ClogService.svc.cs" %>
In my project I'm not supposed to reference ClogService.svc.cs directly right?

Updated Wiki: Home

DanielVaughan — Fri, 07 Nov 2008 07:53:09 GMT

Welcome

Clog now supports Silverlight 2 RTW!

Clog is a customizable log provider system that allows you to harness your existing logging system to log client side messages to your server using WCF or asmx Web Services. Includes Silverlight and WPF sample applications.

Clog is fully customizable, thread-safe, can serialize and log all Exception types, and allows filtering of messages both on the client and server side using custom or inbuilt filters, which so far consists of an IP Address Range Filter, a Role Membership filter, an Environment User Name Filter, a Machine Name Filter, and a Time Range Filter. Includes an extendible Log provider system, a log4net log strategy, a simple tracing log strategy, and a Microsoft Enterprise Library Logging Application Block log strategy.

Clog is a project by Daniel Vaughan

For further information about this project please see

Created Release: Clog v1.6 (Nov 06, 2008)

DanielVaughan — Fri, 07 Nov 2008 07:46:53 GMT

Includes Clog WPF Edition and Clog Silverlight Edition (supporting Silverlight 2 RTW).
Contains source with example projects for Visual Studio 2008 SP1.

Released: Clog v1.6 (Nov 06, 2008)

Fri, 07 Nov 2008 07:46:51 GMT

Includes Clog WPF Edition and Clog Silverlight Edition (supporting Silverlight 2 RTW).
Contains source with example projects for Visual Studio 2008 SP1.

New Post: What about Reloading LogStrategy configuration

lironeizenman — Sun, 28 Sep 2008 13:16:39 GMT

Hi Daniel, Right now Im trying to deal with two issues: 1) Loading Log4Net configuration from XML (or any other strategy). I would like to have in the strategy interface a method that would allow me to do that. Am I missing something or should the implementation should be something like that. 2) Reloading configuration in run time. Actually I want to change the log level of a certain logger at run time, but it seems to appropriate to enable reloading of all the configuration.Again, like in the previous issue, I would like to reload it from the XML configuration file. So, I would like to reload the log4Net config as you understnad. Hope I made the problem clearer. Waiting for your answers, Liron.

New Post: Updated instructions for Configuration ? (and error)

DanielVaughan — Sun, 28 Sep 2008 12:19:59 GMT

GuillaumeJAY,

Yes, I need to update the articles. It’s on my mind. Although, with Silverlight 2 rc1 just out I am keen to update the codebase first.

The CodeBehind attribute won’t disturb compilation, it’s just for Visual Studio.

In regards to the error you are receiving, my advice is to check the ServiceReferences.ClientConfig to ensure its correctness. See the ExampleSilverlightProject for the example.

Thanks for your message, and your kind words.

Cheers,
Daniel

New Post: Updated instructions for Configuration ? (and error)

GuillaumeJAY — Wed, 24 Sep 2008 14:31:38 GMT

This is a great and very needed tool.

It would be very nice if you could update the codeproject article so that the instructions use the last version, WCF service rather than asmx, and so on, more explanations on what must be in web.config.

(BTW, your sample uses " CodeBehind="../../../Clog/Source/Logging/ClientService/ClogService.svc.cs", but I think most people are going to use directly the dll)

I'm currently styck on this error :
The underlying channel factory could not be created because no binding information was found in the configuration file for endpoint with name '*'. Please check the endpoint configuration section with name '*' to ensure that binding information is present and correct.
in :
public ClogServiceClientChannel(System.ServiceModel.ClientBase<Orpius.Logging.ClientLogging.IClogService> client) :
base(client) {
}

Thanks for any help you can give me :)

New Post: What about Reloading LogStrategy configuration

DanielVaughan — Wed, 24 Sep 2008 14:27:45 GMT

Liron,

Do you wish to reload the Log4Net configuration or the Clog Log4NetStrategy configuration?
Perhaps you could tell me a little bit more about the problem you are trying to solve so that I can assist you better.

Just a comment on the second last line of your message...You might want to have a property rather than throwing an exception to signify whether a strategy can reload its config.

Cheers, Daniel

New Post: What about Reloading LogStrategy configuration

lironeizenman — Tue, 23 Sep 2008 16:15:06 GMT

Hi,

Im using the Log4Net strategy. I want to load the configuration from XML and to be able to reload it upon request.

I've been thinking about the right to implement it. I think the right way will be to add two method to the ILogStrategy: LoadConfigurationFromXML, ClearConfiguration.

Each Strategy should implement this methods. if a specific strategy do not approve XML configuration it can throw NotImplementedException.

What do u think ? what other options can you think of ?

New Post: Host in IIS - no client looging

DanielVaughan — Tue, 26 Aug 2008 01:26:49 GMT

The manner in which the endpoint address is constructed from the client config is hardwired for an absolute address, as the following reflector excerpt the internal class ChannelEndpointElement shows:

public void ReadXml(XmlReader reader)
{
    if (reader.MoveToFirstAttribute())
    {
        do
        {
            if (reader.LocalName == "name")
            {
                base["name"] = reader.Value;
            }
            else if (reader.LocalName == "address")
            {
                base["address"] = new Uri(reader.Value, UriKind.Absolute); /* Must be absolute. */
            }
            else if (reader.LocalName == "binding")
            {
                base["binding"] = reader.Value;
            }
            else if (reader.LocalName == "bindingConfiguration")
            {
                base["bindingConfiguration"] = reader.Value;
            }
            else
            {
                if (reader.LocalName != "contract")
                {
                    throw DiagnosticUtility.ExceptionUtility.ThrowHelperError(new InvalidOperationException(string.Format("ConfigUnrecognizedAttribute", reader.LocalName)));
                }
                base["contract"] = reader.Value;
            }
        }
        while (reader.MoveToNextAttribute());
    }
    reader.MoveToContent();
    if (reader.IsEmptyElement)
    {
        reader.Skip();
    }
    else
    {
        reader.ReadStartElement();
        throw DiagnosticUtility.ExceptionUtility.ThrowHelperError(new InvalidOperationException(string.Format("ConfigUnrecognizedElement", reader.LocalName)));
    }
}

So, until this changes we won’t be able to use a relative address when using the ServiceReferences config file for Clog’s configuration.

Your approach seems reasonable for your scenario. One other might be to have a ‘linked’ ServiceReferences.ClientConfig file in your solution, whereby each dev can customize the file. Yet another might be to use a Clog specific config file and perform the configuration of the proxy manually.

Hardwiring Clog to a current page relative address may not suit everybody because Clog may be used to log to a centralised server on a different domain.

Cheers,
Daniel

New Post: Host in IIS - no client looging

jesusgarza — Mon, 25 Aug 2008 18:38:31 GMT

I couldn’t make it work with the web.config change that eranshalley mentions. And because we have several developers working on the same silverlight project, each with its local server, a test server and a production server, we need a way to make the service work, regardless of the server and without touching the ServiceReferences.ClientConfig file.<o:p></o:p>

So we modified the Log class on the SilverlightLogging project to store an EndpointAddress object that points to the page point of origin.<o:p></o:p>

But I would be better if there was a way to define at least the endpoint address from the App, when the silverlight program is starting. The LogManager could store it, since already has a couple of static variables.<o:p></o:p>

<o:p> </o:p>

On the Log constructor we called a method that creates the parameters for the ClogServiceClient:<o:p></o:p>

binding = new System.ServiceModel.BasicHttpBinding();<o:p></o:p>

binding.MaxBufferSize = 2147483647;<o:p></o:p>

binding.MaxReceivedMessageSize = 2147483647;<o:p></o:p>

<o:p> </o:p>

address = new System.ServiceModel.EndpointAddress(<o:p></o:p>

new Uri(Application.Current.Host.Source, "../../ClogService.svc")); //assumes that the service is on root.<o:p></o:p>

<o:p> </o:p>

And we modified the CreateServiceClient method:<o:p></o:p>

ClogServiceClient CreateServiceClient()<o:p></o:p>

{<o:p></o:p>

return new ClogServiceClient(binding, address);<o:p></o:p>

}<o:p></o:p>

New Post: clog and IIS security ,windows integrated

salmanaa — Wed, 06 Aug 2008 12:59:27 GMT

Hi,
I am trying to use clog with windows integrated security configuration, but it is not working for me.

was it tried before?

Thanks
Salman

New Post: Host in IIS - no client looging

eranshallev — Thu, 10 Jul 2008 09:26:20 GMT

Daniel,

The 1_1_5 release works fine (checked on XP, IIS6).

q:
ServiceReferences.ClientConfig is part of .xap file.
my concern is how to modify the endpoint address after deploy (on production).
We managed to do that by setting the address in the Web.config file - which overides the configuration in the ServiceReferences.ClientConfig:

endpoint address="http://localhost/clog/ClogService.svc" binding="basicHttpBinding" contract="Orpius.Logging.IClogService">

is that the approach you recommend?

Thanks
Eran

New Post: Host in IIS - no client looging

DanielVaughan — Wed, 09 Jul 2008 06:50:16 GMT

Eran,

Are you using IIS 7 on Vista by any chance? If you are and you are using the default (IPv4) ranges specified in the example web.config, then the filter will prevent logging. In any case, comment out the filters for troubleshooting.
I’ve released a new version, which I have tested on IIS 7 on Vista. The only change required when publishing is to modify the ServiceReferences.ClientConfig file in the ExampleSilverlightProject project to match your deployment url.

Sorry for the delay in responding.

Cheers,
Daniel

RELEASED: Clog v1.1.5 (Jul 09, 2008)

Wed, 09 Jul 2008 06:14:22 GMT

Includes Clog WPF Edition and Clog Silverlight Edition (supporting Silverlight 2 Beta 2).
Contains source with example projects for Visual Studio 2008 RTM.

Changes

Silverlight Log Debug information improved.
Silverlight LogViewer Internal Message display added.

CREATED RELEASE: Clog v1.1.5 (Jul 09, 2008)

Wed, 09 Jul 2008 06:14:22 GMT

Includes Clog WPF Edition and Clog Silverlight Edition (supporting Silverlight 2 Beta 2).
Contains source with example projects for Visual Studio 2008 RTM.

Changes

Silverlight Log Debug information improved.
Silverlight LogViewer Internal Message display added.

New Post: Host in IIS - no client looging

eranshallev — Thu, 03 Jul 2008 12:33:49 GMT

Daniel,

I should add to the first post:
when the Client app attempts to log, i.e. Orpius.Loggimg.Silverlight attempts to call the ClogService, an exception is thrown:

"Unhandled Error in Silverlight 2 Application Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)\n
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)\n
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)\n
at System.Delegate.DynamicInvokeImpl(Object[] args)\n
at System.Delegate.DynamicInvoke(Object[] args)\n
at System.Windows.Threading.DispatcherOperation.Invoke()"

maybe that gives some insight.

Regards
Eran