Internalization not happening completely

[sivak4Net]

In our project, we previously used ILRepack.Lib.MSBuild.Task version 2.0.18.2, which successfully merged all dependent assemblies and converted their types to internal. This behavior was critical for avoiding type conflicts, especially with commonly used libraries like Newtonsoft.Json.

Recently, we upgraded directly to version 2.0.43, and observed a change in behavior: not all types from merged assemblies are being converted to internal. For example, classes from Newtonsoft.Json remain publicly accessible in the merged output, as highlighted in the attached image. This is causing conflicts on the consumer side, since clients may also reference Newtonsoft.Json independently.

While converting Newtonsoft.Json to a dependent package is technically feasible, our requirement is to deliver a fully bundled library due to the diversity in client environments (.NET versions and frameworks). Therefore, we need a solution that ensures all merged types are internalized, as was previously possible.

Any guidance or support on resolving this issue with the latest ILRepack version would be greatly appreciated.

ILRepact.targets:

[ravibpatel]

Are you using the custom targets file or using the library as it is with bundled targets file?

[sivak4Net]

I found the root cause of why internalization was not happening: the public methods exposed through my APIs were preventing the classes/enums from being converted to internal.

After fixing this issue, I ran into another problem. I’m unable to embed the public key (.snk) into the merged assembly. I followed the steps exactly as described in the readme.md, by defining the key file path in the IlRepack.config.props and referencing that path in the ILRepack task within the IlRepack.targets.

However, I keep getting a “Keyset does not exist” error. I verified that the .snk file is present, and if I change anything related to the .snk file path in IlRepack.config.props, it immediately reports that the file does not exist at that path. I also checked all file permissions, and everything looks good.

[ravibpatel]

If you are using custom IlRepack.targets then you don't need to define it in IlRepack.config.props. Just reference it directly in your ILRepack.targets file. You can see how I did that in the default target file here.

KeyFile="Your Key file path"

[sivak4Net]

Done the same thing but still getting the Keyset does not exist error

[ravibpatel]

Can you provide your targets file so I can try on my end?