So I can pass a delegate into GetAll.
Then I can overload GetAll and not break the existing.
I'll think that is a good way Frans
[EMAIL PROTECTED]
> Date: Wed, 21 Nov 2007 11:23:33 +0100> From: [EMAIL PROTECTED]> Subject: Re:
> [ADVANCED-DOTNET] Code review>
CTED] Behalf Of Paul Cowan
Sent: Wednesday, November 21, 2007 4:33 AM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: Re: [ADVANCED-DOTNET] Code review
That is a good point about the ordering of roles.
That is definitely flaky.
But I will still be left with the inline if statements.
Can I som
7;s
abit shaky, as the service is a resource you're using in a different context C
which has the security rules of C, but another context C' has perhaps
different rules.
FB
>
>
>
> > Date: Wed, 21 Nov 2007 09:49:15 +0100> From: [EMAIL PROTECTED]> S
t; [ADVANCED-DOTNET] Code review> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > > I
> am writing an ASP.NET application that is heavily influenced by users and> >
> roles. I am finding my code becoming increasing cluttered with the>
> following> > typ
> I am writing an ASP.NET application that is heavily influenced by users and
> roles. I am finding my code becoming increasing cluttered with the
following
> type of thing:
> IList businessFunctions;
> if (CurrentUser.RoleIsAbove(Role.BusinessUnitAdmin))
> {
> if (CurrentUser.IsSystemAdmin)
>
Hi all,
I am writing an ASP.NET application that is heavily influenced by users and
roles. I am finding my code becoming increasing cluttered with the following
type of thing:
IList businessFunctions;
if (CurrentUser.RoleIsAbove(Role.BusinessUnitAdmin))
{
if (CurrentUser.IsSystemAdmin)
