If you add the logging configuration into a config file named Rhino.ServiceBus.Host.exe.config, then the host will pick it up and use it automatically.
I've needed to do this in the past for assembly binding redirects. Miles On Fri, Apr 19, 2013 at 7:21 AM, René M. Andersen < [email protected]> wrote: > We are having some trouble getting exceptions logged, which happens in the > startup phase of the Rhino Service Bus when using the > Rhino.ServiceBus.Host.exe to host our service. The issue was found in > 2.3.4 and 3.0.0. > > The problem seems to be that logging is never initialized in the main > appdomain which hosts the remote appdomain with our service. Exceptions > thrown during startup is caught and attempted to be logged in the following > method in RhinoServiceBusHost.cs: > > protected override void OnStart(string[] ignored). > > > But since the logging framework is not initalized, valueable debugging > infomation gets lost. > > Any suggestions on work arounds or can it be fixed so that logging is > initialized? > > Regards > > René > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
