I have a VS.NET 2003 solution with a project for a ServicedComponent (lives
in a COM+ Server Application for object pooling) and a project for MSI
making. Both build fine and I get an MSI.
I went back and added this to the ServicedComponent-inheriting class:
// Ensure that writing to the Event Log can only be done to the local
machine and cannot delete
// logs or sources from the Registry
[assembly:
EventLogPermissionAttribute(
SecurityAction.RequestOptional , MachineName="." ,
PermissionAccess=EventLogPermissionAccess.Instrument )
]
And while both projects continue to compile fine, I then get this when I run
the MSI:
"
Unable to create an instance of
net.atomic9.SeachWorker.SearchWorkerInstaller installer type --> Exception
hasa been thrown by the target of an invocation. --> Security error.
"
The MSI is installed under the local Administrator account. What can I/not
do to set CAS on my component?
Thanks.
* Bonus - if I switch to a NAnt task for making an MSI, will I run into the
same problem?
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
