I am using the SolidEdge.Community.AddIn to create a C# addin.
Using the Register-SolidEdgeAddIn with the package manager works great but when I try to deploy using
regasm /codebase on another machine it does not succeed.
RegAsm : error RA0000 : Could not load file or assembly 'SolidEdge.Community.Add
In, Version=184.108.40.206, Culture=neutral, PublicKeyToken=null' or one of its depen
dencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131
My assembly is strong named but the community dlls are not.
Is there a particular reason or benefit that you are trying to attain by signing your assemblies? I've seen pro\con arguments over the years regarding open source assembly signing. There just hasn't been a need to this point to sign them. I'll update my knowledge on the topic and see what our options are.
It start with the error I recieved when I attempted to register my addin outside of my development environment. Registration was failing and it stated that the SolidEdge.Community.AddIn needed a strong name.
I believe the problem has gone away after I removed and added the nuget packages.
It may be permissions related but I was registering under the administrator account.
I think I am all set now. Think I just spun out for a moment.