I have an app that uses Queued Components.  The queue is set as
transactional and the transaction is set to Supported (I've also tried
Required).  Everything is running on the same box (tried XP and 2k3).  In my
app I wrap the queued component call in a TransactionScope.  I'm ...

apologies in advance if this topic has already been covered, but my
search in the newsgroups has yet to reveal the secret formula.
I've got a .NET C# application that invokes a classic C++ .DLL using
DllImport.   I'm working at source level with both .NET and the C++

I have written an application in .NET 2 (I also have .NET 1 installed).
Until a few days ago, I could use regsvcs without any problem in order to
installed my serviced assemblies in COM+. All of a sudden, when I tried it
today, I got "You must have administrative credentials to ...

I'm a little bit confused with this new System.Transactions namespace.
I was able to understand its propose, but it looks like it is the
replacement for EnterpriseService (ServicedComponent) when all you want
from COM+ is the transaction coordination.

  I have a Com+ component in C# which has a method as follows:
public XmlElement CreateRequest ( string loanNumber );
This method creates a request using XmlDocument object and returns
XmlDocument.DocumentElement which is basically an XmlElement. Now after

I have a COM+ application with one object that is never destroyed. Each time
I run the client application that uses it, the a new instance of the object
is created. Even though the object is set to null by the client, it never
gets garbage collected. The only way to destroy the ...