Giters

darrencauthon / AutoMoq

Auto mocking provider for Moq.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Strong name the assembly

powerdude opened this issue · comments

commented

Please strong name the assembly.

commented

I have two quick questions:

1.) Why? And I ask that seriously, as in all of my years of .Net development, I've never had to mess with strongly-named assemblies. And since this library is only used in test assemblies, which are not released to production, I never understood why a strong name would matter.

2.) Is this something you could do and release as a pull request ? Is this a minor change?

commented

Well, i may be unique in this case, but on a project where i'm trying this out, all dlls are signed, and it's enforced on the build server.

I don't have the infrastructure set up to use git, but the steps are simple.

  • Run "sn -k automoq.snk" to create the strong name file
  • Tick a check box in the properties of the project on the signing tab and select the file you just created.
  • done (i think)

cliff

commented

Ok, I'll add this to my list of things to hit on this project. I'll do what I can, but if this affects using it in an "unsigned" way, then I won't be able to make the change.

Have you tried signing it yourself, using your own copy and dll?

commented

yes, i have.

On Tue, Dec 6, 2011 at 10:43 PM, Darren Cauthon
reply@reply.github.com
wrote:

Ok, I'll add this to my list of things to hit on this project.  I'll do what I can, but if this affects using it in an "unsigned" way, then I won't be able to make the change.

Have you tried signing it yourself, using your own copy and dll?

Reply to this email directly or view it on GitHub:
#12 (comment)

thanks

cliff

commented

I'm cleaning up tasks, and looking back at this: I don't understand it. I've never worked in such an environment, and I just can't do it unless I understand it.