[ ] support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
Assemblies don't have strong names.
What is the expected behavior?
All assemblies have strong names (All assemblies are signed).
What is the motivation / use case for changing the behavior?
We have test assemblies and they are signed with strong name, so we cannot reference to your unsigned assemblies (for ex. Allure.NUnit and Allure.SpecFlow). We sign assemblies, because we need access to internal classes of assemblies of our systems (signed company policies). We cannot make internal classes as public by design and security.
I'm submitting a ...
What is the current behavior?
Assemblies don't have strong names.
What is the expected behavior?
All assemblies have strong names (All assemblies are signed).
What is the motivation / use case for changing the behavior?
We have test assemblies and they are signed with strong name, so we cannot reference to your unsigned assemblies (for ex. Allure.NUnit and Allure.SpecFlow). We sign assemblies, because we need access to internal classes of assemblies of our systems (signed company policies). We cannot make internal classes as public by design and security.
Please tell us about your environment: