App.config for Queued Component in .NET

[Izo...@nospam.nospam]

If I add assembly that contains queued component implementation to GAC as I
am required by documentation, then where am I supposed to put app.config
file for that DLL?

[WenJun Zhang[msft]]

Hi,

I've seen a former case and the solution is QC creates its own AppDomain,
specifies the config file and invokes the method that uses that config
file, but there is no more details on it. An alternative and more
recommended solution should be using a custom config file and manually
parse it. The following .net examples may shed some light on this:

Per-Assembly Configuration Files
http://www.theserverside.net/developmentor/thread.tss?thread_id=25076

Per-Assembly Configuration Files ported to VB
http://codebetter.com/blogs/darrell.norton/archive/2004/01/15/5646.aspx

Please update if you have any further questoin.

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Frank Boyne]

<Izo...@nospam.nospam> wrote in message
news:9A5C52D1-28EB-482C...@microsoft.com...

> If I add assembly that contains queued component implementation to GAC
> as I am required by documentation, then where am I supposed to put
> app.config file for that DLL?

I don;t think your question really makes sense in this context. An
application configuration file can only be defined for an executable,
not for a DLL.
http://msdn.microsoft.com/en-us/library/aa374182(VS.85).aspx

[Izo...@nospam.nospam]

Ok, solution with reading settings directly does not look all that promising
unless I misunderstand it.

I use System.Diagnostics.TraceSource, System.Diagnostics.BooleanSwitch and
WCF. That means that I have the following standard configuration tags in
app.config:
- system.diagnostics
- system.serviceModel

Does it mean I have to load configuration for these classes with my own code
because of GAC requirment for COM+?

This is quite inconvenient, time consuming and bug prone.

""WenJun Zhang[msft]"" <wjz...@online.microsoft.com> wrote in message
news:YSU9uPj8...@TK2MSFTNGHUB02.phx.gbl...

[WenJun Zhang[msft]]

This does seem to be a bit fussy and inconvenient. I just wonder if you are
using .net serviced component to create the COM+ application and configure
it as a queued component for reliability with MSMQ? If so, why not consider
implementing it directly as a WCF web service with bindings like
MsmqIntegrationBinding or NetMsmqBinding?

Integration and Migration of COM+ services to WCF
http://msdn.microsoft.com/en-us/library/bb978523.aspx

[Izo...@nospam.nospam]

Retry functionality is a reason why we use COM+ queued components. The
typical scenario is database or network is down, so we want message to be
re-tried at a later time automatically until it goes to a dead queue.

It is my understanding that IIS host can not provide this type of
functionality.

""WenJun Zhang[msft]"" <wjz...@online.microsoft.com> wrote in message

news:4M2L5s69...@TK2MSFTNGHUB02.phx.gbl...

[WenJun Zhang[msft]]

Actually some WCF bindings hosted by IIS like WSHttpBinding also supports
reliable messaging. It simply achieves this by implementing acknowledge
mechanism on the communication stack. See:

Introduction to Reliable Messaging with the Windows Communication Foundation
http://msdn.microsoft.com/en-us/library/aa480191.aspx

Using WCF MsmqIntegrationBinding or NetMsmqBinding can fully achieve the
same MSMQ retry behavior you look for since both of them are based on MSMQ
as underlying transport. Also you will not be annoyed by the config file
anymore.

As you know, COM+, Queued Component are deprecated technologies comparing
to .Net and WCF and Serviced Component is designed for backwards
compatibility only. Since you've already used WCF, I'd strongly recommend
you give up QC and switch to a decent WCF solution.

Please let me know if you have further concern on this.

Have a great day.

[Izorich]

I found the solution I was looking for:

http://blogs.msdn.com/b/heikkiri/archive/2005/11/10/491568.aspx