Services without Components (SWC) and ServiceConfig Bug??


So I’m developing a serviced component in C#, and this component is intended to model mixed mode transactional capability, in that some methods will be transactional and some not. Therefore the component is configured in COM+ as Transactions: Disabled.

The transactional methods will use SWC ServiceConfig to create a transactional context in which to perform work.

The problem I’ve found concerns use of the Inheritance property;

– If I set the property to Ignore, a new context is created which is not transactional (ContextUtil.IsInTransaction = false) and security is not enabled in the new context (which I would expect).

– If I set the property to Inherit, a new context is created which again is not transactional (ContextUtil.IsInTransaction = false) but this time security is enabled in the new context (fair enough, new context inherits this from existing context).

– If I don’t set the property at all, a new context is created which is transactional (ContextUtil.IsInTransaction = true) and security is not enabled in the new context (not sure what to expect at this point since I’ve not specified Ignore or Inherit).

The documentation states that this property defaults to “Inherit“, from my experience this doesn’t seem to be bourne out – is it a bug.

I’ve trawled the internet and not found anything, anyone else come across this??

My environment: XP Pro SP2, VS.NET 2003 SP1, .NET v1.1.4322

Published by

Phil Harding

SharePoint Consultant, Developer, Father, Husband and Climber.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s