|
-
Aug 26th, 2003, 02:30 AM
#1
Thread Starter
Fanatic Member
Deploying COM+ components...
Which attributes take precedence if there are discrepancies between how a component is coded in VB and how it is configured in the Component Services MMC snap-in?
eg. If I set the MTSTransactionMode in my VB Component to "RequiresNewTransaction" but then click the Transactions "Not Supported" option in the MMC snap in how is this resolved?
If I write a component which is not intended to be stateless and do not call GetObjectContext.SetComplete or SetAbort at the end of SomeMethod() but then check the "Automatically deactivate this object when this method returns" box in the Com+ Methods property dialog what happens then?
Thanks in advance for any help!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|