strongname

问题 Within my Visual Studio solution I have a web site and 4-5 class library projects which are referenced., some of which reference external third party assemblies as well. I've been given the task of signing the assemblies for these projects. My understanding is that the purpose of signing is that not everyone being able to use our assembly without providing its public key and version details, right? Should I use one single Strong Name Key (.snk) to sign all the assemblies of these projects or

问题 I've read this claim in many places and had people tell me this directly, but I haven't been able to find a conclusive answer about the full list of reasons why a Strong Name can't be used for security. I understand the intention of the Strong Name feature is identification rather than security but I'm looking for an explanation of any security problems that can be caused by using Strong Naming for security. I'd like to know: What the CLR does out-of-the-box with respect to verifying Strong

问题 I'm trying to build an application that is strongly named. It is referencing a COM interop library that I add via the Add References dialog. It's been a while, but I seem to recall that in older versions of visual studio, there was a project setting for Wrapper Assembly Key File . I can't seem to find it in Visual Studio 2008? 回答1: I came across your post looking for the same thing, but found a different route on my own to get around the issue of strong naming a COM Interop referenced

问题 I have no experience developing C++ on Windows, but I am a C# developer. I have a wrapper around some native DLLs that is written in C++. (A LGPL project)). I was to use this from a strong named assembly. How do I set up the strong naming of the C++ assembly? There is no 'Signing' properties tab available as there is in C# projects. I imagine that I need to edit the vcproj file and put a reference to the key file, something like /KEYFILE:"sgKey.snk" that I found at this site: http://www

问题 I am trying to load a third party COM dll into my application. Everything builds fine but when I run the application I keep getting this message from my application: Could not load file or assembly '"assembly", Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044). When I do a sn -vf "assembly" it says the assembly is valid. Has anyone seen this type of behavior before? 回答1: The assembly

问题 I am trying to load a third party COM dll into my application. Everything builds fine but when I run the application I keep getting this message from my application: Could not load file or assembly '"assembly", Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044). When I do a sn -vf "assembly" it says the assembly is valid. Has anyone seen this type of behavior before? 回答1: The assembly

问题 My application consists of three assemblies: a single EXE which references a couple of DLLs. The DLLs are private to my application - they are used only by this executable. Should these assemblies be given a strong name? FxCop suggests that they should - for all of the assemblies it currently produces: CA2210: Sign <assembly> with a strong name key. However, this advice says: In general, you should avoid strong-naming application EXE assemblies. and you may want to avoid strong-naming

问题 I am trying to find way to use the strong name sign as an configuration. My case is: I have project that it include in two different solution. For one solution I want that the project will be sign with strong name key, but for the other solution I want that the project will be without sign. Currently I declare the signing throw: project->properties->signing. 回答1: OK, I got it, just edit proj file manually <PropertyGroup Condition="'$(SolutionName)' == 'SolutionToSign' "> <snip />

问题 I am trying to find way to use the strong name sign as an configuration. My case is: I have project that it include in two different solution. For one solution I want that the project will be sign with strong name key, but for the other solution I want that the project will be without sign. Currently I declare the signing throw: project->properties->signing. 回答1: OK, I got it, just edit proj file manually <PropertyGroup Condition="'$(SolutionName)' == 'SolutionToSign' "> <snip />

问题 How can I load an assembly using its full display name from a location outside the application's bin path? Usually one can load an assembly from a custom location with Assembly.LoadFrom(path); This works, but it seems that for loading a strong-named assembly I need to specify its full display name such as in Assembly myDll = Assembly.Load("myDll, Version=1.0.0.1, Culture=neutral, PublicKeyToken=9b35aa32c18d4fb1"); But the problem here is that this only references assemblies that are in my