Divine.Sdk

Build with automatic SDK updates

On Windows, use build-sdk-update.cmd instead of dotnet build when the build should automatically restart after a global.json update:

build-sdk-update.cmd path\to\project.csproj -c Release
build-sdk-update.cmd path\to\solution.slnx -c Release

The command forwards the build arguments unchanged and sets DivineSdkAutoRestart=true. It retries only the SDK update signal DIVSDK001, up to three attempts. Other build failures are returned immediately. Each retry starts a new dotnet build process so the updated SDK configuration is loaded before project evaluation.

The loaded Divine SDK version is printed from its task assembly's version, which comes from the project's Version property in four-part numeric format. The .NET SDK version comes from MSBuild. When an SDK configuration update triggers a retry, the previous attempt's SDK versions and changes are printed before restarting; the final attempt prints its loaded versions again.

The output of the final attempt and its exit code are returned. Output is buffered while each attempt runs. Temporary build logs are deleted when the command finishes normally.

The NuGet package includes this command at tools/build-sdk-update.cmd. A plain dotnet build continues without an automatic restart; SDK updates take effect on the next build.