C# SDK - A strongly-named assembly is required

Dan Britton

Edit - I started from scratch rebuilding it, and that solved whatever bug was causing the issue.  I still have no idea what was wrong.

 

I'm using Visual studio/C# to make a dll for Office/VBA automation.  This was working until the TLS 1.0 deprecation on 3/31.   I updated the SDK to to the newest version using the NuGet manager in Visual Studio.  My code compiles, but I get the following warning:

• 1>CSC : warning CS8002: Referenced assembly 'smartsheet-csharp-sdk, Version=2.6.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

I've strongly-named my dll, but how do I get a strongly-named Smartsheet assembly that my dll references?  Without it, VBA throws an error when the dll is referenced.

dAVE Inden

Looking into this I found a post on StackOverflow that may help you get passed this error here:

https://stackoverflow.com/questions/331520/how-to-fix-referenced-assembly-does-not-have-a-strong-name-error

I'd like to be able to track this further and discuss it with our developer on the C# SDK. Can you open an issue with your question on the Github repo for the C# SDK?

https://github.com/smartsheet-platform/smartsheet-csharp-sdk/issues

dAVE Inden

I wanted to follow up here. Our C# SDK isn't code signed, so using it with a strongly named assembly won't work. You may have previously gotten this to work if you built the SDK from source using your own certificate. Signing it yourself is also covered in the StackOverflow post I gave previously.