Reactiveui: [BUG] Universal Windows Application fails to build in Release with ReactiveUI

[SuperJMN]

Universal Windows Application fails to build in Release with ReactiveUI

Steps To Reproduce

1. Create a blank Universal Windows Application.
2. Add the ReactiveUI package (latest version 10.1.6)
3. Change the configuration to Release
4. Change the platform to x86 or x64.
5. Build the application.
6. You should get an error like this:

error : ILT0005: 'C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\runtime.win10-x86.microsoft.net.native.compiler\2.2.7-rel-27913-00\toolsx86\ilc\Tools\nutc_driver.exe @"C:\Users\JMN\source\repos\App6\App6\objx86\Release\ilc\intermediate\MDIL\App6.rsp"' returned exit code 1

Expected behavior
Build successful

Environment

• OS: Windows 10 x64
• Version 18362.356
• Device: Windows Desktop

Additional context
Targeting:
Target version: Windows version 1903
Min. version 1809

[open-collective-bot[bot]]

Hey @SuperJMN :wave:,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider contributing financially.

https://opencollective.com/reactiveui

PS.: We offer priority support for all financial contributors. Don't forget to add priority label once you start contributing :smile:

ReactiveUI - Open Collective

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!

[glennawatson]

Updated to UWP 6.2.9 as part of #2167 -- this should solve your issue if not respond back to this issue.

[SuperJMN]

Sadly, the issue is still there :( I'm attaching a solution with the issue.

App6.zip

I've seen the Task Manager during the build process and from some point, it starts to consume a lot of memory. That can be what ultimately produces the issue, as stated by @MattWhilden here https://twitter.com/SuperJMN/status/1172949559267475456?s=20 (see the answers)

Twitter

José Manuel Nieto on Twitter

“@WhildyBeast @ziki_cz @arcadio_g_s @windowsdev Hey thanks! I've built my solution (Release) and the following errors have been shown (pasted them in Notepad for convenience). Is this enough to know what's the cause? Thanks, Matthew!”

[SuperJMN]

Workaround

Cause

It seems the problem is that the compiler used during the build process is a 32-bit process + it uses a huge amount of RAM to do its job.

Fix

The 64-bit version of the compiler doesn't fail. We can force to use it instead the 32-bit compiler using this XML element inside the .csproj file of the affected project:

<Use64Bitcompiler>true</Use64Bitcompiler>

It should be added to the first PropertyGroup element of the file.