Re: COM+ Method level security problem
- From: BSmith <BSmith@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 13:32:02 -0700
Imports System.Runtime.InteropServices
Imports System.EnterpriseServices
<ClassInterface(ClassInterfaceType.AutoDual), _
ComponentAccessControl(), SecureMethod()> _
Public Class ClientServices
Inherits System.EnterpriseServices.ServicedComponent
Public Function CreateNewClient(ByVal Name As Object) As Integer
Dim sql As String
Dim NewID As Integer
sql = gBuildStoredProcSQL("ClientAddNew", Name)
NewID = gExecuteWithSingleResult(sql)
Return NewID
End Function
<SecurityRole("AppUser")> _
Public Function FetchClient(ByVal ClientID As Integer)
Dim sql As String
sql = gBuildStoredProcSQL("ClientFetch ", ClientID)
Return gExecuteWithResults(sql)
End Function
<SecurityRole("AppSuperUser")> _
Public Function FetchClientAccounts _
(ByVal ClientID As Integer) As DataTable
Dim sql As String
sql = gBuildStoredProcSQL("ClientAccountsFetch", ClientID)
Return gExecuteWithResults(sql)
End Function
End Class
.
- Follow-Ups:
- Re: COM+ Method level security problem
- From: Gabriel Lozano-Morán
- 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
- COM+ Method level security problem
- Prev by Date: Re: Correct deployment scenario for serviced components - IIS and MSSQ
- Next by Date: Re: COM+ Method level security problem
- Previous by thread: Re: COM+ Method level security problem
- Next by thread: Re: COM+ Method level security problem
- Index(es):
Relevant Pages
|