Skip to content

Debugging Traditional Bridge Code

Jump to bottom
Jeff Greene edited this page Jul 19, 2021 · 7 revisions

Harmony Core Logo

Debugging Traditional Bridge Code

This brief video provides an overview of the steps necessary to debug the traditional Synergy code that is running behind a Harmony Core Traditional Bridge implementation.

VIDEO: Creating a Basic Solution

Please be aware that there was an issue in versions 11.1.1d and 11.1.1e of Synergy that prevented remote debugging working with Harmony Core Traditional Bridge implementations, but this issue has been resolved in the up-coming 11.1.1f release.

Detailed error messages from SignalR

Inside your routine/lambda that is passed to the AddSignalR method you can add code similar to the following

if(string.Compare(Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT"), "Development") == 0)
   options.EnableDetailedErrors = true

if(Debugger.IsAttached)
   options.ClientTimeoutInterval = 4096

When the APNETCORE_ENVIRONMENT is set to development, signalR will now produce helpful error messages instead of just telling you that the invocation failed. Additionally bumping up the timeout interval during debugging is commonly helpful.

Clone this wiki locally