.NET 1.1: Problems with StrongNameIdentityPermissionAttribute

From: Markus Wildgruber (msdngroups_at_syska.de)
Date: 05/05/03

  • Next message: Andrew Snyder: "DES, 3DES, and AES performance" 
    Date: Mon, 5 May 2003 15:27:51 +0200

    Hi!

    In our solution we use the StrongNameIdentityPermissionAttribute to assure
    that only callers signed with certain public keys get access to some of our
    methods.
    So we applied the StrongNameIdentityPermissionAttribute twice to that
    methods with two different public keys.
    That worked in version 1.0 of the .NET Framework.
    Now, when we first tried to compile the project in version 1.1 using VS.NET
    2003 we got some errors (Common language runtime internal error:
    0x8013144e).

    After we removed one of the attributes from the methods we can build the
    project without any problems.

    Does anyone know a solution?

    TIA,

    Markus

  • Next message: Andrew Snyder: "DES, 3DES, and AES performance"

    Relevant Pages

    • Re: .NET 1.1: Problems with StrongNameIdentityPermissionAttribute
      ... is that in v1.1 the compiler actually reports an error instead of just ... > In our solution we use the StrongNameIdentityPermissionAttribute to assure ... > methods with two different public keys. ...
      (microsoft.public.dotnet.security)
    • Re: .NET 1.1: Problems with StrongNameIdentityPermissionAttribute
      ... The difference between the versions> is that in v1.1 the compiler actually reports an error instead of just> letting it sit there and do nothing. ... > "Markus Wildgruber" wrote in message ... >> In our solution we use the StrongNameIdentityPermissionAttribute to assure>> that only callers signed with certain public keys get access to some of> our ... >> methods with two different public keys. ...
      (microsoft.public.dotnet.security)
    • Quantcast