# IronRuby and Strong Name Verification Skipping

**URL:** <https://www.ruby-forum.com/t/ironruby-and-strong-name-verification-skipping/142853>\
**Category:** IronRuby\
**Created:** [July 12, 2008, 4:12am UTC](https://www.ruby-forum.com/t/ironruby-and-strong-name-verification-skipping/142853 "2008-07-12T04:12:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![acampos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/919ad9/32.png) [@acampos](https://www.ruby-forum.com/u/acampos)\
**Post date:** [July 12, 2008, 4:12am UTC](https://www.ruby-forum.com/t/ironruby-and-strong-name-verification-skipping/142853/1 "2008-07-12T04:12:01Z")

</div>

Hi All,

I was wondering if anyone could shed any light on how strong names,  
assembly signing and verification skipping is working with IronRuby now?

After checking out the latest version of IronRuby from svn I was able to  
build ok but when running any application that used IronRuby (including  
the ir console) I would get assembly load errors normally to do with the  
fact that a Microsoft.Scripting could not be found, the error related to  
the fact that a signed version of the assembly could not be found.

After a quick look around I found the SIGNED compilation option and  
switched that off but that didn’t help. I then tried to turn off  
assembly signing in for each of the IronRuby assemblies in [VS.Net](http://VS.Net) 2008.  
That didn’t work but it seems to be a bug in [VS.Net](http://VS.Net) becuase even though  
I unticked the option to sign the assemblies the build would fail if I  
moved the key that [VS.Net](http://VS.Net) supposedly shouldn’t have been looking for. So  
I then resorted to editing the project files to remove all options  
relating to strong naming and that worked. I was able to get  
applications to load the assemblies and run correctly.

That was about a month ago and I have since re-checked out the IronRuby  
code and thought it would be better to get this string naming thing  
sorted out. Initially I hit all the same problems and then happended  
upon the command below in runfirst.cmd:

sn -Vr \*,31bf3856ad364e35

After running that command all the apps that use IronRuby (including the  
ir console) work fine with the default signed assemblies. But if you  
have to turn off assembly strong name verification to get the IronRuby  
assemblies to load what’s the point of signing them in the first place?

Regards,

Aaron

---

<div class="post-metadata">

**Author:** ![acampos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/919ad9/32.png) [@acampos](https://www.ruby-forum.com/u/acampos)\
**Post date:** [July 12, 2008, 4:26am UTC](https://www.ruby-forum.com/t/ironruby-and-strong-name-verification-skipping/142853/2 "2008-07-12T04:26:33Z")

</div>

The key that is in SVN is only a test key. If you notice, the solutions  
are  
set up to DELAY sign, not FULLY sign. Any delay signed assemblies have  
to  
be registered for verification skipping. This is a common development  
technique to ensure the build scripts and everything work correctly,  
without  
having to put your true key out in the wild.

When Microsoft officially releases IR, they will fully sign it using a  
true  
private key.

On Fri, Jul 11, 2008 at 10:12 PM, Aaron C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![acampos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/919ad9/32.png) [@acampos](https://www.ruby-forum.com/u/acampos)\
**Post date:** [July 12, 2008, 2:49pm UTC](https://www.ruby-forum.com/t/ironruby-and-strong-name-verification-skipping/142853/3 "2008-07-12T14:49:23Z")

</div>

Michael L. wrote:

> The key that is in SVN is only a test key. If you notice, the solutions  
> are  
> set up to DELAY sign, not FULLY sign. Any delay signed assemblies have  
> to  
> be registered for verification skipping. This is a common development  
> technique to ensure the build scripts and everything work correctly,  
> without  
> having to put your true key out in the wild.
> 
> When Microsoft officially releases IR, they will fully sign it using a  
> true  
> private key.
> 
> On Fri, Jul 11, 2008 at 10:12 PM, Aaron C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

Perfect. Thanks for the explanation.