Hello
I am trying to encapsulate a .dll inside a nuget package. The package should be able to use it, but consumers of the package should not know about the .dll (trying to solve https://stackoverflow.com/questions/79263758/how-to-use-bouncycastle-fips-library-in-conjuction-with-bouncycastle-cryptograph)
When I use 'internalize' flag, I can no longer access the assembly. (Which makes sense). But is there some way to specify which projects may access the internal namespace? (similar to InternalsVisibleTo?)
Hello
I am trying to encapsulate a .dll inside a nuget package. The package should be able to use it, but consumers of the package should not know about the .dll (trying to solve https://stackoverflow.com/questions/79263758/how-to-use-bouncycastle-fips-library-in-conjuction-with-bouncycastle-cryptograph)
When I use 'internalize' flag, I can no longer access the assembly. (Which makes sense). But is there some way to specify which projects may access the internal namespace? (similar to InternalsVisibleTo?)