[CSHARP-142] Mongodb DLL's do not have strong name Created: 23/Dec/10  Updated: 05/Apr/19  Resolved: 03/Mar/11

Status: Closed
Project: C# Driver
Component/s: None
Affects Version/s: 0.9
Fix Version/s: 1.0

Type: Task Priority: Major - P3
Reporter: Erinc Assignee: Robert Stam
Resolution: Done Votes: 1
Labels: question
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I downloaded the latest c# driver release, have been playing around with it for the last couple of hours, I can't get my project to build without errors, I keep getting

Assembly generation failed – Referenced assembly 'MongoDB.Driver' does not have a strong name

for both of the dll's. I tried disassembling the dll's using ildasm.exe and tried assembling the output file using ilasm.exe with a strong key, I keep getting a failure message. I don't know if it's a problem about dll's, I wanted to check with you. Can you please tell me what to do, is there anything that I am missing to get it working?

If you can get back to me from erincarikan@gmail.com;

I'd really appreciate it.

Happy holidays

Erinc



 Comments   
Comment by Robert Stam [ 03/Mar/11 ]

Assemblies are now signed using a TemporaryKeyPair which is included in the source files stored in github. By storing the TemporaryKeyPair in github we make it possible for you to build signed assemblies directly from the files in github. However, this means the private key of the TemporaryKeyPair is not secure. If you want to sign your custom builds more securely you can generate your own strong name key. We intend to re-sign the official DLLs with a different strong name key when we make official releases.

Comment by Robert Stam [ 23/Dec/10 ]

The Bson and Driver DLLs are not currently signed (i.e. do not have a strong name). You are probably getting this error message because you are referencing the DLL from an assembly of your own that is signed. .NET won't let a signed assembly reference an unsigned assembly.

Your short term options are:

1. Change your assembly to unsigned, if you can
2. Download the source code and modify the projects to sign the DLLs with a temporary strong name key of your own

We intend to sign the assemblies eventually.

Generated at Wed Feb 07 21:35:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.