Jacques Eloff

There's a property called ```GenerateAssemblyFileVersionAttribute``` that defaults to true. If you want to manage the file version, you can set this to false.

You can try creating a binlog and then searching for the version. That looks very much like a commit SHA. Are you using any versioning packages, e.g. Nerdbank.GitVersioning?

with msbuild, or dotnet build you can pass /bl. There's a special msbuild binlog viewer available to view the files: https://msbuildlog.com/

There's an extension available called Project System Tools, but I've never used it.

The EXE is part of the MSI  Let me dig around some more

Latest release installs fine  @LostBeard can you share the MSI log? I'm guessing you just ran the MSI directly, so it will likely be under your %temp% directory in...

I've confirmed, it's a problem with the upgrade. @LostBeard for now, just repair the MSI. The 1.6.0 build is bad. The file version for `dotnet-core-uninstall.exe` is 42.42.42.42424 (that's the default...

MSI logging might be turned off. There's a policy key you can query from a command prompt using `reg query HKLM\SOFTWARE\POLICIES\Microsoft\Windows\Installer /s` You should see something like ``` HKEY_LOCAL_MACHINE\SOFTWARE\POLICIES\Microsoft\Windows\Installer Logging...

I think we may need to update some of the tests, but still investigating... ``` 》CSC : warning MSTEST0001: Explicitly enable or disable tests parallelization (https://learn.microsoft.com/dotnet/core/testing/mstest-analyzers/mstest0001) [C:\h\w\A9410983\t\dotnetSdkTests\2cwojbxj.idv\6fcc3159-12e0---FBCD72DF\TestProject\TestProject.csproj] 》C:\h\w\A9410983\t\dotnetSdkTests\2cwojbxj.idv\6fcc3159-12e0---FBCD72DF\TestProject\Test1.cs(17,4): warning MSTEST0025:...

~~So looks like the test locally is failing with "exit code 5", but the regex is looking for exit code 8.~~ The test outputs are different. TestProject/OtherTestProject have the expected...