A private repository controls access to source. It does not decide what someone can learn from the application you distribute.
Managed binaries contain metadata and intermediate language that inspection tools can expose. The exact result depends on the application, runtime and the protections applied. This makes the shipped artifact part of the release review.
Start with the boundary
Ask three questions before choosing a protection profile:
What information does this release expose that matters to our business?
Which transformations can the application tolerate?
What evidence would let us trust the output?
These are separate questions. A transformation can make an application harder to inspect and still break a feature it needs.
Compatibility is part of protection
Reflection, serialization, plugins and dynamically discovered types deserve particular attention. Test the actual supported route with a non-confidential sample first.…