Re: COM+ Method level security problem
- From: "Gabriel Lozano-Morán" <gabriel.lozano@xxxxxxxxxxx>
- Date: Wed, 27 Apr 2005 23:27:16 +0200
> Is this method required in all cases or is it a workaround
> - if not then why does the Interface generated by VS (with
> Register for Com interap optin checked) not work?
Because you use method level security you need to explicitly declare an
interface.
> *at first it didn't work but second time it did - is it
> possible COM+ is caching dll's somewhere - I had COM+ admin
> consol open the first time?
this is called object pooling and can be disabled with the attribute
objectpooling (see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemEnterpriseServicesObjectPoolingAttributeClassTopic.asp)
but use it wisely :)
Some articles you can read about COM+:
http://msdn.microsoft.com/msdnmag/issues/01/10/complus/
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadvnet/html/vbnet11262002.asp
Gabriel Lozano-Morán
.
- Follow-Ups:
- Re: COM+ Method level security problem
- From: anonymous
- Re: COM+ Method level security problem
- References:
- COM+ Method level security problem
- From: Brendon
- Re: COM+ Method level security problem
- From: Gabriel Lozano-Morán
- Re: COM+ Method level security problem
- From: BSmith
- Re: COM+ Method level security problem
- From: Gabriel Lozano-Morán
- Re: COM+ Method level security problem
- From: Brendon
- COM+ Method level security problem
- Prev by Date: Re: COM+ Method level security problem
- Next by Date: How to reference a remote DLL
- Previous by thread: Re: COM+ Method level security problem
- Next by thread: Re: COM+ Method level security problem
- Index(es):
Relevant Pages
|