strongname

I'm working on a C# application which uses the EasyHook library for DLL Injection. EasyHook requires that any application using it be strongly named. In order to strongly name the application I need to make sure that all the libraries I use are strongly named as well. This is easy to do for all of my managed libraries, but I also have an unmanaged c++ library which I need to strongly name. After some searching I can't seem to find a way to sign my unmanaged dll, even with the source code. Can this be done, and if so what do I need to do? Thanks for any suggestions or assistance! I assume that

I'm trying to sign a .net core lib, and I'm just not sure if I did everything correctly 1) using VS Command Promp I called sn -k mykey.snk 2) copied mykey.snk to myproject folder 3) in project.json added keyfile "frameworks": { "netstandard1.6": {} }, "buildOptions": { "outputName": "MyLib", "keyFile": "mykey.snk" } is this correct, is the library (dll) going to be usable on both .net core and full .net 4.6 apps ? Yes, this is the correct way. If you look into any ASP.NET Core projects, like Logging , you will find "buildOptions": { "keyFile": "../../tools/Key.snk" ... } in project.json file,

I have a project, and I created a strong name key file for it. How can I tell what the strong name of my assembly is? It seems this should be obvious, but I can't find any reference to it. You can get the Fully Qualified Name by using a tool like Reflector or ILSpy. Select the assembly and it should be in top of it. For XNA in ILSpy : // C:\Program Files (x86)\Microsoft XNA\XNA Game Studio\v4.0\References\Windows\x86\Microsoft.Xna.Framework.dll // Microsoft.Xna.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=842cf8be1de50553 If you don't want to use those tools, you can figure out

I have a unmanaged C++ dll, which will be used by a managed C++/CLI wrapper .dll, which will eventually be used by a C# project. C# project is strong-named, so is the wrapper .dll. I tried doing the same for the unmanaged dll, using /KEYFILE, but doesn't seem to work. And the wrapper is complaining: .... is a strong-name signed assembly and embedding a manifest invalidates the signature Do I need to strong-name the unmanaged C++ at all? If not, how do I resolve this issue? It is not possible to strong-name a native DLL. Most of all because doing so is meaningless, only the CLR will ever

I manage an open-source project and would like to sign the binaries that are released in the project's binary package. I use Visual Studio csproj and sln files to manage and build my project, and also distribute these files as part of the project's source packages. How can I sign the produced binaries of my build and not have to distribute the snk key-pair file? If I use Visual Studio to sign the assemblies, each project file now needs a copy of the key-pair in order to build. I'm not comfortable with distributing the key-pair, even if it is password protected. Edit : Another caveat is that

A colleague of mine created an assembly in VB.net for use with JScript via COM interop. The assembly used to work fine, but we signed it and now it only seems to work on Windows 7 machines. I've tested 2 Windows 7 machines and 2 Windows Vista machines. When we signed the assembly and we try to instantiate the ActiveX object in JScript, an error is returned with no message and only a number: Error: Error number: -2146234304 A search on Google for the error number didn't return much. If we remove the strong name from the assembly, it works just fine. Any ideas on what could be the problem? Not