Return to Answer

Active reading.

edited Dec 27, 2019 at 15:22

Just one more cause of a slow Visual Studio debugging experience...

Long time ago I enabled FusionLog to see what was causing an assembly binding problem.

Make sure you disable it after using it. Why? Because it writes a lot of logging data to the disk while enabled.

This is the FusionLog key on Window's Registry [ (regedit.exe ]):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Change the ForceLog, LogImmersive and LogResourseBindings values from 1 enabled(enabled) to 0 disabled(disabled).

Just one more cause of a slow Visual Studio debugging experience...

Long time ago I enabled FusionLog to see what was causing an assembly binding problem.

Make sure you disable it after using it. Why? Because it writes a lot of logging data to the disk while enabled.

This is the FusionLog key on Window's Registry [ regedit.exe ]:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Change ForceLog, LogImmersive and LogResourseBindings values from 1 enabled to 0 disabled.

Just one more cause of a slow Visual Studio debugging experience...

Long time ago I enabled FusionLog to see what was causing an assembly binding problem.

Make sure you disable it after using it. Why? Because it writes a lot of logging data to the disk while enabled.

This is the FusionLog key on Window's Registry (regedit.exe):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Change the ForceLog, LogImmersive and LogResourseBindings values from 1 (enabled) to 0 (disabled).

answered Aug 29, 2014 at 22:16

Just one more cause of a slow Visual Studio debugging experience...

Long time ago I enabled FusionLog to see what was causing an assembly binding problem.

Make sure you disable it after using it. Why? Because it writes a lot of logging data to the disk while enabled.

This is the FusionLog key on Window's Registry [ regedit.exe ]:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion

Change ForceLog, LogImmersive and LogResourseBindings values from 1 enabled to 0 disabled.