You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
After referencing the Scintilla.NET NuGet package (v5.6.1/v5.6.0) in our project, we encountered a build issue indicating that a strong name is required. Below is the mentioned error occurred while building the solution.
error MC1000: Unknown build error, 'Could not load file or assembly 'Scintilla.NET, Version=5.6.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A Strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
Describe the solution you'd like
Request to include the strong naming for the assemblies used while referring to the nuget package.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
I think the workaround of forking the repo and making that a signed version would be a better idea than trying to incorporate it into this one...but I am open to other ideas.
I haven't researched what it would take to add it to the project so I'll take a look at what that entails. It would be a nice to have, I just haven't looked into the possible issues it could cause yet.
Is your feature request related to a problem? Please describe.
After referencing the Scintilla.NET NuGet package (v5.6.1/v5.6.0) in our project, we encountered a build issue indicating that a strong name is required. Below is the mentioned error occurred while building the solution.
error MC1000: Unknown build error, 'Could not load file or assembly 'Scintilla.NET, Version=5.6.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A Strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
Describe the solution you'd like
Request to include the strong naming for the assemblies used while referring to the nuget package.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: