Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Handling COM Interop with EnterpriseServices

Status
Not open for further replies.

tEkHEd

IS-IT--Management
Jan 29, 2003
261
GB
Hi all..

I am trying to get my head around the COM+ Interoperability with .NET and was wondering if someone could point me in the right direction here...

Basically I have coded a DLL with a simple function to run a process (using the .NET Process class).

I have found that I can dynamically install the DLL and set certain attributes if I inherit from the ServicedComponent class.

There are 2 issues that I currently have:

1: I have defined the role/s to setup in my application by defining them in the objects' AssemblyInfo

Code:
<Assembly: ApplicationAccessControl(True)> 
<Assembly: SecurityRole("myUser")>

I need to understand how I can now add user accounts to this role and setup the role access on my objects' methods.

2: I have defined that the object be run as a ServerComponent again in the AssemblyInfo

Code:
<Assembly: ApplicationActivation(ActivationOption.Server)>

How can I now define that this process be run as a Service, and supply the context under which the process will run? I cannot seem to find any attribute that allows this.

A further (slighly minor) question that I have is; when the assembly is compiled and installed when I open Component Services and expand my Com Application. I am unable to see the methods that are exposed although I can succesfully call and execute them. Does anyone know why this is? The Functions are declared as PUBLIC.

Many thanks for your assistance.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top