Build script does not syncronize build times #1

New Issue

2026-08-19T10:12:40+01:00

2026-08-19 10:12:40 +01:00

Building close to the minute change can lead to builds of the app with different version IDs, leading to confusion.

This is due to the csproj file containing

<AssemblyVersion>$([System.DateTime]::UtcNow.ToString("yyyy.MMdd.HHmm"))</AssemblyVersion>

I have no clue how to fix this, perhaps caching the build time and somehow overriding this tag during compilation? But this would then break locally created builds which would need the unique timestamp and to not be reliant on BUILD.py.

Perhaps there is a dotnet argument to override specific values from csproj files? I'll look into this in the morning.

Building close to the minute change can lead to builds of the app with different version IDs, leading to confusion. This is due to the csproj file containing ```xml <AssemblyVersion>$([System.DateTime]::UtcNow.ToString("yyyy.MMdd.HHmm"))</AssemblyVersion> ``` I have no clue how to fix this, perhaps caching the build time and somehow overriding this tag during compilation? But this would then break locally created builds which would need the unique timestamp and to not be reliant on BUILD.py. Perhaps there is a dotnet argument to override specific values from csproj files? I'll look into this in the morning.

paradoxical_autumn added the bug confirmed labels 2026-08-19 10:12:40 +01:00

paradoxical_autumn self-assigned this 2026-08-19 10:12:40 +01:00

paradoxical_autumn closed this issue

2026-08-19 10:12:40 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: paradoxical_autumn/mc-manager#1