Re: Signing effects

From: Andreas Claudi (ask@and_i_will_tell.com)
Date: 03/28/03

  • Next message: Amit Saxena: "Writing to a mapped folder" 
    From: Andreas Claudi <ask@and_i_will_tell.com>
Date: Fri, 28 Mar 2003 00:00:52 -0800

    I have a service in assembly S.
    This service makes use of a LicenceChecker module L - also in a seperate
    assembly.
    L is signed and S references it.

    If I make a clean build there is no problem, but if I rebuild L alone and
    copy it to the run directory of S, I get a 'does not match manifest'-etc.
    exception when starting S.

    My primary concern is to ensure that
    a) S is not changed to remove the call to L's verification method
    b) L is not changed to just return true

    Can this be achieved by signing both assemblies?
    In my understanding, this is not enough. Possibly Link Demand is the
    answer?

  • Next message: Amit Saxena: "Writing to a mapped folder"

    Relevant Pages

    • Re: Problem with late databinding and GAC
      ... I am using the fully qualified object name. ... and there is a project reference to it. ... Does the object reside in a seperate assembly? ... >> I have my Business Logic and Facade assemblies in the GAC, ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Sharing Code
      ... But this is a red-herring you've thrown in and really has nothing to do with the general precept and good practice of signing any assembly you create because it is *the easiest thing to do* when creating the most flexible of assemblies. ... How are you making it sound oh so time consuming to add a reference to a key file when you know damn well it takes seconds, which in any normal developer's book is zero-effort. ... in order to avoid warnings I moved the signing from AssemblyInfo to the properties pane. ...
      (microsoft.public.dotnet.languages.csharp)
    • Re: strong name error
      ... Conditionally signing of assemblies is still possible, ... Remove all assembly-level attributes previously used to specify signing ... Specify your preferred signing behaviour for release builds using the ...
      (microsoft.public.dotnet.framework)
    • Re: Run app from network share
      ... For this, and to run applications in the security zone of network shares, we're signing our .NET assemblies with a strong key that is shared by all products from our company. ...
      (microsoft.public.dotnet.framework)
    • Re: Delayed Signing, the GAC, and Installations
      ... > for signing the assemblies. ... > should handle the signing of the assemblies before generating the ... signing assemblies or generating installation packages, ... the content list for a setup project. ...
      (microsoft.public.dotnet.framework.aspnet.security)