Experimenting with transactions, and trying to disable part of them by
deleting the relevant refererence in Component Services, I have come to the
conclusion that something in COM+, perhaps the Distibution Transaction
Coordinator, appears to cache components that execute sucessfully.

Thus when you delete a reference to a component that is part of a
transaction in Component Services, and run the transaction again, the
transaction still works fine. This should not happen.

Even if I restart my machine, this transaction still appears to work fine
though the reference to one of its components has been deleted from Component
Services.

There must be some sort of Cache here. How do I stop this cache from
operating, or induce it to refresh, or whatever?

Thanks

Ian

"Ian" <(E-Mail Removed)> schrieb
> Experimenting with transactions, and trying to disable part of them
> by deleting the relevant refererence in Component Services, I have
> come to the conclusion that something in COM+, perhaps the
> Distibution Transaction Coordinator, appears to cache components
> that execute sucessfully.
>
> Thus when you delete a reference to a component that is part of a
> transaction in Component Services, and run the transaction again,
> the transaction still works fine. This should not happen.
>
> Even if I restart my machine, this transaction still appears to work
> fine though the reference to one of its components has been deleted
> from Component Services.
>
> There must be some sort of Cache here. How do I stop this cache from
> operating, or induce it to refresh, or whatever?
>
> Thanks


Have a look @ one of these groups for language unrelated questions:
microsoft.public.dotnet.framework.*


Armin