I have a .Net DLL with a COM-Callable wrapper which is called by an MSMQ
trigger. I am trying to implement logging in this DLL using the
My.Application.Log class, and for this I need the the DLL to load a
configuration file with a <system.diagnostics> section in which I hope to add
custom trace listeners in future. The configuration file needs to be loaded
when the DLL assembly is initialized, not via the ConfigurationManager, and
to do this I am trying to create a new AppDomain, with  an AppDomainSetup
object pointing to a config. file. The problem I am getting is that the
object created in the new AppDomain is throwing security exceptions when
trying to log to file/event viewer. Is this caused by the MSMQ trigger
service mqtgsvc.exe not being trusted or having enought security permissions.

Any help on how to tackle this or whether this is the best approach would be
much appreciated.

ASP.Net Framework 2.0 not showing up as an IIS property page
How to deploy this .net dll to staging?
.NET Framework 2.0 Configuration
DateTime.ParseExact weird behavior
Embedding a resource at runtime