Re: COM+ Method level security problem
- From: <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Apr 2005 08:46:32 -0700
Thanks - I've got another question regarding
programatically detecting roles, but I'll post as a new thread.
>-----Original Message-----
>> 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
>
>
>.
>
.
- 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
- Re: COM+ Method level security problem
- From: Gabriel Lozano-Morán
- COM+ Method level security problem
- Prev by Date: Re: Problem with Path.GetTempFileName
- Next by Date: COM+ querying roles applied to methods
- Previous by thread: Re: COM+ Method level security problem
- Next by thread: Visual Studio COM reference
- Index(es):
Loading