TestOnlyProductBehavior infrastructure used in installer tests patches codesigned binaries on macos resulting in test failuress.

[VSadov]

I wonder if we could set some environment variable to enable test features instead of patching a guid inside the binary.

Tagging subscribers to this area: @vitek-karas, @agocke
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	VSadov
Assignees:	-
Labels:	area-HostModel, untriaged, needs-area-label
Milestone:	-

[vitek-karas]

Just curious - why we can't resign the binary after the modification?

The general idea around this "test only product behavior" was to make it as close to 0 cost as possible at runtime when disabled. The static variable is kind of the next best thing after modifying the executable code itself which would be even more complex.

But I'm definitely open to ideas here - it's always been a bit of a sore spot.

[vitek-karas]

Also of note - the current design means that I can't get a dotnet.exe signed by MS to work differently, since the binary modification will invalidate the signature. Similarly for hostfxr.dll and so on. While this might be a complex thing to handle in testing, it alleviates basically any security concerns around this "test only" feature.