By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,330 Members | 1,262 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,330 IT Pros & Developers. It's quick & easy.

CodeAccessSecurityAttribute and named parameters of type System.Type

P: n/a
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <OO**************@TK2MSFTNGP05.phx.gbl>
Newsgroups: microsoft.public.dotnet.languages.csharp
NNTP-Posting-Host: kooijma1.dsl.vianetworks.nl 212.61.93.147
Lines: 1
Path: border1.nntp.dca.giganews.com!nntp.giganews.com!ne wsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.cw.net!cw.net!news-FFM2.ecrc.de!TK2MSFTFEEDS01.phx.gbl!TK2MSFTNGP01.p hx.gbl!TK2MSFTNGP05.phx.gbl
Xref: number1.nntp.dca.giganews.com microsoft.public.dotnet.languages.csharp:422879

Hi,

I'm working on the authorization subproject of our framework, and
defined a class that derived from CodeAccessSecurityAttribute. One of
its named parameters is of type System.Type (actually, it should've been
a required constructor parameter, but CodeAccessSecurityAttribute
doesn't work if you define your own constructors).

When applying the attribute to a class(-member) however, whenever I use
the named parameter of System.Type I get a COMException with message
"Unsupported type for field or property setter. (Exception from HRESULT:
0x8013144A)" somewhere after the constructor is run.

Is this a known issue? expected behaviour?

thanks in advance,

--
Willem van Rumpt
May 12 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.