Using finBL.DebugLaunch

Monday, 14 July 2025 by Matthew Bowers

With the release of finPOWER Connect version 6, the platform moved from the .NET Framework to .NET Core. This shift requires extra configuration in Visual Studio for finBL.DebugLaunch to operate as expected. On a fresh Visual Studio installation, you may notice that finPOWER continues running when using finBL.DebugLaunch, even while stepping through code. If this happens, you will need to disable the following setting in Visual Studio by navigating to Tools > Options > Debugging > General:

  • Disable "Enable address-level debugging"
  • Disable "Enable Just My Code"

The quickest way to access this setting is by navigating to Tools > Options and entering "debugging" in the search box. The options that need to be disabled will typically appear as the first two items in the list.

Note that if you need to use DebugLaunch with a version of finPOWER Connect earlier than version 6, you will need to re-enable the "Enable address-level debugging" setting.

If you regularly work with both version 6 and older versions of finPOWER Connect, consider installing multiple instances of Visual Studio - using one for version 6 and another for earlier versions. Visual Studio settings are independent across different installations. We recommend using the latest version of Visual Studio for debugging finPOWER Connect version 6.

As of finPOWER Connect version 6, finBL.DebugLaunch also behaves slightly differently. The following will now occur:

  • The Script you are debugging will now be converted to C# for debugging. This is a Visual Studio issue and as of the date of this blog, there is unfortunately no way to configure the Debugger to launch the script as VB in Visual Studio.