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
{{ message }}
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.
Assemblies initialiy compiled with [assembly: AllowPartiallyTrustedCallers] lost this attribute after merge.
Steps to reproduce:
Create new class library project (targetFramework: 3.5)
Add line "[assembly: AllowPartiallyTrustedCallers]" to AssembliInfo.cs
Call ILMerge by "Ilmerge /out:out.dll ClassLibrary1.dll /targetplatform:v2" command
open out.dll in ILSpy or Reflector or any other tool
Observed: there is no 'AllowPartiallyTrustedCallers' assembly attribute
Expected: AllowPartiallyTrustedCallers attribute should be specified for the assembly (like in original ClassLibrary1.dll).
The text was updated successfully, but these errors were encountered:
I found the source code which implements this restriction (it's easy to find), and posted on StackOverflow to ask why this restriction was introduced into the code -- Why does ILMerge delete security-related attributes?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Assemblies initialiy compiled with [assembly: AllowPartiallyTrustedCallers] lost this attribute after merge.
Steps to reproduce:
Observed: there is no 'AllowPartiallyTrustedCallers' assembly attribute
Expected: AllowPartiallyTrustedCallers attribute should be specified for the assembly (like in original ClassLibrary1.dll).
The text was updated successfully, but these errors were encountered: