localization vs strong names RRS feed

  • Question

  • I have a strong named dll assembly with some controls. It seems to me that by default satellite assemblies have to be signed with the same key as the main assembly to load properly. The questions are:
    1. Is it really the case?
    2. Is there any way to provide users of my library to create their own translations for my library (other than not signing my assembly with strong name at all)?
    Tuesday, February 16, 2010 11:13 PM


  • Hi, TomaszGrobelny:
         To answer your questions:
         1. If your main assembly is strong named, your satellite assemblies must be signed with the same private key. Check here for more details.
         2. I don't think it's possible for you to strong-name sign your assembly first and then let the end-user add satellite assembly for localiztion purpose. Since your private key is not published to the end-user, their localized satellite assemblies cannot be properly strong-name signed and thus cannot be used by the main assembly. But maybe you could consider Delay Signing an Assembly, which defers the actual signing until some later stage (typically just before shipping the assembly).

         Here are some refs may help you:
        1. Security and Localized Satellite Assemblies
        2. Delay Signing an Assembly
    Please mark the right answer at right time.
    Wednesday, February 17, 2010 8:06 AM