RE: Cannot change Code Group's Membership Condition to Strong Name
From: Shawn Farkas (shawnfa_at_online.microsoft.com)
Date: 03/04/04
- Next message: Gary K: "Dumb Q - Signing an assembly"
- Previous message: Shawn Farkas: "RE: Strong names between exe and dll"
- In reply to: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Next in thread: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Reply: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 04 Mar 2004 02:08:18 GMT
If you're calling into Excel you'll need unmanaged code permission, and if you're doing much with threads you'll probably need control thread
permission. These are both flags on the SecurityPermission itself (SecurityPermisisonFlag.ControlThread |
SecurityPermissionFlag.UnmanagedCode)
-Shawn
http://blogs.msdn.com/shawnfa
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they
originated.
--------------------
>Thread-Topic: Cannot change Code Group's Membership Condition to Strong Name
>thread-index: AcQBghOxDAn4nLASQDWP0IQIxFnBDA==
>X-Tomcat-NG: microsoft.public.dotnet.security
>From: =?Utf-8?B?TG93ZWxs?= <theyas@theyas.com>
>References: <5E252D81-1F8C-4BDA-B89C-AF99DE703D67@microsoft.com> <xwWA8LLAEHA.616@cpmsftngxa06.phx.gbl>
>Subject: RE: Cannot change Code Group's Membership Condition to Strong Name
>Date: Wed, 3 Mar 2004 16:46:06 -0800
>Lines: 68
>Message-ID: <A72801B0-F76B-4CA2-ADEF-A8729F9D6D34@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.dotnet.security
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.security:5234
>NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
>X-Tomcat-NG: microsoft.public.dotnet.security
>
>Thanks Shawn. That helped! Now I'm back to my other problem. My UI object instantiates a "worker" object in another DLL and calls a method
in it. The "worker" object instantiates an "Excel Interface" object and calls a method in it. The last method call fails with a "Security error." and the
stack trace shows the last method call (from the "Excel Interface" object). But when I debug and step into or set a breakpoint just inside the method
itself, I neveractually get inside that method even though the arguments passed to the method are native types (strings, ints and bools). (Note that I
can get into the constructor without any trouble, it's just when I try to drill down into that first method that everything stops.)
In my "worker" object, I've created extra methods so that I can "Assert" all the permissions I think I need. I'm "Asserting" a "ReflectionPermission",
a "FileIOPermission", a "SecurityPermission", and a "WebPermission" (I'm reading data from a Webservice).
Note that when I run the UI object from a Windows EXE object, everything (of course) works just fine.
Any ideas as to what that "Security Error" might be? (The try/catch catches a "SecurityException" which has "Security Error" for the "Message", the
Stack Trace has the method I never get into and and the method with the catch, and blank "PermissionState", "PermissionType" and
"PermissionsRefused" properties.)
TIA
----- \"Shawn Farkas\" wrote: -----
Hi Lowell,
I wrote a blog about this topic. You can find more information here:
http://blogs.msdn.com/shawnfa/archive/2003/06/26/57026.aspx
-Shawn
http://blogs.msdn.com/shawnfa
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they
originated.
--------------------
>Thread-Topic: Cannot change Code Group's Membership Condition to Strong Name
>thread-index: AcQAEfvtwhx9M+JuTU+b0Q19jJrFcQ==
>X-Tomcat-NG: microsoft.public.dotnet.security
>From: =?Utf-8?B?TG93ZWxs?= <theyas@theyas.com>>Subject: Cannot change Code Group's Membership Condition to Strong Name
>Date: Mon, 1 Mar 2004 20:51:11 -0800
>Lines: 9
>Message-ID: <5E252D81-1F8C-4BDA-B89C-AF99DE703D67@microsoft.com>>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.dotnet.security
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.security:5206
>NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
>X-Tomcat-NG: microsoft.public.dotnet.security
>>I've got a web client DLL that I run through IE using the <Object> tag. When I define the Membership Condition using a "Site" or a "URL" in
mscorcfg, it works (well, part way, see previous post). When I change the Membership condition to a Strong Name, nothing works. The DLL's
UI
doesn't even come up in the browser.
The structure of the DLLs are as follows: A "UI.dll", which calls a "Doit.dll", which calls a "Util.dll" and the Excel XP PIA dlls. My three dlls are all
strong-named from the same keypair.snk file. The Excel XP PIAs are also strong-named, by Microsoft. I set up the strong name Memebership
Condition with just the public key (I grabbed the public key by importing from the "UI.dll")
Any ideas how I can get this working or how I can trouble-shoot it?
Thanks!
Lowell
>
>
- Next message: Gary K: "Dumb Q - Signing an assembly"
- Previous message: Shawn Farkas: "RE: Strong names between exe and dll"
- In reply to: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Next in thread: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Reply: Lowell: "RE: Cannot change Code Group's Membership Condition to Strong Name"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
