Feature: Enable/Disable Fusion Logging

[yannduran]

@madskristensen do you think enabling/disabling Fusion logging would be useful for extensibility authors? I haven't used it myself, but I thought you'd know better than most.

I saw it mentioned in the MEF Error Log:

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[madskristensen]

I just talked to the engineering manager on my team about that. His concern was that, given how expensive it is running with Fusion enabled, it should probably not be something that is easy to do. Another of his concerns was that if people uninstall your extension, how would they know how to disable it again.

Perhaps either just put it in the description of your extension, or add a command that opens the browser to a URL that shows how to do it manually by setting the registry key.

[MagicAndre1981]

how expensive it is running with Fusion enabled,

this is why I always use ETW (Microsoft-Windows-DotNETRuntimePrivate provider with FusionKeyword keyword (0x4)) to trace fusion issues only on demand in case I run into issues.