Skip to content

Arch Forum 2025-11-19

Participants: Backend devs, Andy, Kyle, and Victor

Agenda

  • Remove dev configs
  • ERR logs
  • ArgoCD demo
  • New platform features
  • Unified Directory.Build.props file
  • VS2026
  • .NET 10

Summary

Remove dev configs

We don't need to keep be-configuration/src/dev and similar folders in be-cde-configuration, be-risk-configuration, and be-mf-configuration around anymore.

Result: No opposition. Victor will clean it up.

ERR logs

A reminder: it is important to remember that there are more log levels than TEKM. For example, when deploying, do not forget to also check for ERR and WARN logs (or any other suspicious logs).

ArgoCD Demo

A demo of the most useful parts of ArgoCD. An overview is at ArgoCD

New platform features

  • EIN EventSender: The sender of an event is now logged in Kibana/Elastic as "EventSender" in the object field for EIN logs. This will be the ApplicationId when a service publishes an event, if the event is manually inserted into the MessageOutbox table it will be the user's login name unless explicitly set.
  • DateOnly / TimeOnly DB support: It's now possible to use DateOnly / TimeOnly types in the DB repositories.
  • Outbox Metrics to DD: The outbox now publishes metrics to DD, with the name minority.outbox.messages.
  • CSV configs: Platform now supports ConfigurationSourceType.Csv, allowing CSV files as configuration files.

A good idea came up when looking at the CSV feature: It would be great if one of the PR checks in the be-configuration repos validated that any JSON and CSV files are not malformed.

Unified Directory.Build.props file

We want to unify various csproj settings over backend. The Directory.Build.props file helps to make all projects in a repo use the same settings. An example in be-platform is here.

To not force documentation in all projects (which is what happens by default by setting GenerateDocumentationFile), we will also change the diagnostic setting to not force comments on all public types and members.

[*.cs]
dotnet_diagnostic.CS1591.severity = suggestion

VS2026

With .NET 10 Microsoft released VS 2026.

IDE usage questions:
- How many use VS?
- How many use ReSharper in their VS?
- How many upgraded to VS 2026?
- What else do you use?

Notes:
- Some are already using VS 2026, without ReSharper.
- Some mainly use VS Code and only VS as a backup.
- Some use Rider.
- Some use VS 2022, with or without ReSharper.

As a result Andy will optimize our ReSharper licenses. Anyone that finds it useful is encouraged to use it. But if you don't need it, then we shouldn't pay for a license.

.NET 10

Microsoft recently released .NET 10 & C# 14. We will upgrade as soon as possible (in relation to other priorities).
(When we upgrade we will also get .NET 9 / C# 13.)

Overview of .NET 10 and C# 14
(and .NET 9 and C# 13)

Some of the new things we might want to explore once we are on .NET 10 everywhere:
- Microsoft.Testing.Platform
- SLNX solution format

Ozan was interested in investigating .NET 10 and C# 14 and will take the lead.

The previous upgrade to .NET 8 was tracked in Jira epic MP-450. The upgrade to .NET 10 will be tracked in Jira epic MIB-13707