Files
marekf a79622eb15 <Fix>: Align TBF projects with .NET Framework 4.8, increase revision to 3.9.3147.126
Cause:

- TBF was upgraded from .NET Framework 4.7.2 to 4.8 for Laatzen and GCI compatibility in commit 6199bd48c, while ResultsBrowser remained on 4.7.2 despite referencing TBF.
- Introducing PackageReference for MySql.Data exposed this existing framework mismatch during package restore, producing NU1201 errors.
- Other Framework projects, application startup configurations and the Workplace installation prerequisite still targeted or declared older Framework versions.

Solution:

1. Align project target frameworks
   - Upgrade ResultsBrowser and 36 remaining projects from .NET Framework 4.7.2 to 4.8.
   - Update SDK-style projects from net472 to net48.

2. Align runtime and installation requirements
   - Update 20 application startup configurations to require .NET Framework 4.8.
   - Update the Workplace bootstrapper prerequisite to .NET Framework 4.8.

3. Increased revision
   - Updated AssemblyVersion and AssemblyFileVersion from 3.9.3147.125 to 3.9.3147.126.
2026-10-28 14:18:44 +01:00
..

AppDiagnostic.Logging

Reusable NLog target for sending structured diagnostic events from multiple .NET Framework processes to AppDiagnostic.exe through a local named pipe.

Producer integration

Reference this project from the producer application and add the extension and target to its NLog configuration:

<extensions>
  <add assembly="AppDiagnostic.Logging" />
</extensions>

<targets>
  <target name="appDiagnostic"
          xsi:type="AppDiagnostic"
          layout="${message}" />
</targets>

<rules>
  <logger name="*" minlevel="Trace" writeTo="appDiagnostic" />
</rules>

The target writes to a bounded background queue. Producer threads are not blocked while the diagnostic viewer is unavailable. Queued messages are sent after the viewer becomes available; new messages are discarded when the queue limit is reached.

The receiver can read messages with:

DiagnosticLogEntry entry =
    DiagnosticMessageSerializer.ReadFramed(namedPipeServerStream);