Closed jonathanpeppers closed 1 month ago
I don't think even Release
builds need a unique build id, as far as we are concerned. The Guids we care about are the assembly MVIDs, and that only in Release builds when marshal methods are enabled. So we should be fine forcing the same build id in Debug
(I wouldn't force it in Release
, as something else somewhere may expect the id to be different).
Android framework version
net9.0-android
Affected platform version
.NET 9
Description
I was testing our incremental build and noticed:
An incremental build of a MAUI project, where I changed either C# or XAML
This value changes each time:
This generates a new
obj\Debug\net9.0-android\android\environment.arm64-v8a.ll
each time, causing us to run_CompileNativeAssemblySources
each time.Could we use the same Guid for most
Debug
builds? Would onlyRelease
builds need a unique Guid?/cc @grendello
Steps to Reproduce
dotnet new maui
Did you find any workaround?
No
Relevant log output
hellomaui_Debug_AnyCPU_Build_2024-08-16T11_28_53.1332631-05_00.binlog.zip