It is a best practice to Strongly-Name assemblies to prevent assembly conflicts.
We had an issue that our private NuGet package failed because it was strongly named and could not make use of the DD4T NuGet packages (since they are not). Our fix was to remove our strong name from our NuGet package to solve it. I hope this is a temporary solution.
It is a best practice to Strongly-Name assemblies to prevent assembly conflicts.
We had an issue that our private NuGet package failed because it was strongly named and could not make use of the DD4T NuGet packages (since they are not). Our fix was to remove our strong name from our NuGet package to solve it. I hope this is a temporary solution.
(This applies to all DD4T packages, btw)