I understand the basic idea behind signing assemblies but have a problem when using Telerik or 2rd party DLLs.
I\'ve spent an hour debugging this, and I finally eliminated the PEBCAK issue. I have an internationalized application. A key part of the application uses reflection to load types from configured sou
I\'m getting an error trying to sign a dll in F# on mono: $ mono /usr/local/share/FSharp-2.0.0.0/bin/fsc.exe\\
I have a windows application that that a lot of dependant DLLs. When I publish this application it returns an error for one of the DLLs that it must be strongly signed in order to be mark开发者_Python
I have a problem which I\'m pretty sure that I can\'t solve without going back to the vendor, but I thought I would float the problem here first.
If I\'m deploying an asp.net mvc app, do I need to sign my DLLs?They 开发者_高级运维won\'t be placed in the GAC.No, but Microsoft do recommend signing every assembly as is it well-recongised as good p
Right now I am setting the Linker/Advanced/KeyFile option. I am getting the \"mt.exe : general warning 810100b3:is a strong-name signed assembly and embedding a manifest invalidates the signature. Yo
For various reasons i would rather not use strong named (signed) assemblies in my project. however, one of the projects is referenced by a sharepoint web part which means it must be signed.
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
In the visual studio project settings you can choose a strong name key file for signing the assembly. When creating a new one you can choose to protect it with a password. When should you do this? And