Open Ruud-cb opened 5 years ago
I have found out that the Package page does not honor the Solution Configuration. It turns out it is going back from ReleaseUwp to normal Release and therefor seems to build my unrelated android project. When I disable the build option for the default 'Release' Solution Configuration and try again, all works fine. I guess I should move this problem elsewhere?
Hi,
I am having a lot of trouble on this time consuming process where creating UWP (sideloaded/upload) packages, it fails a lot of times. I have tried to do the following steps to reduce the likelyhood of other factors playing a role in the problem:
I will not start complaining about the build times of the release building that takes more then 10 minutes, but just focus on the actual problem.
This is how the Solution Configuration is showing. The errors start to appear when I try to build a x64 release via the Publish => Create App Packages
The problem seems that it is trying to build projects that are not selected in the Solution Configuration. For example currently the project
Babywatcher.App.AndroidApp
is not building successfully in x64 architecture (or it uses AnyCpu, that is not clear). Although I didn't select that project in the Solution Configuration, it still throws errors.A complete log file (set to Normal) when I build the ReleaseUwp on x64 via Solution -> Rebuild Solution. See logsnormalbuild.txt
A complete log file (set to Normal) when I build via Publish -> Create App Packages. See logspublishbuild.txt
I have used the following configuration on the publish page:
And here are the error messages I am getting:
I got this error in one of the previous builds:
I have got this error in the last build:
In red I have marked a few projects that are not selected in the Solution Configuration.
As you can see I am getting
Xamarin\Android
related errors, which are currently, certainly, not in the selected projects's dependencies. All the selected projects besides theWindowsApp
WindowsApp.Package
andWindowsApp.Bridge
are all .net standard packages and don't have a reference to Xamarin.And to end up with a mind-blown statement: When I ONLY select x64 during publish, I was able to create a package successfully! So can it be an issue when building for both x86 and x64 after each other?
Project file of the UWP Package app, the main executable.
Directory contents:
Command line
See log file for this, I don't know which of the 1000 commands you are looking for
Expected behavior
I would expect that only the selected projects within the Solution Configuration are being build when creating an UWP package.
Actual behavior
It seems that other projects are also being build when creating UWP packages.
Environment data
msbuild /version
output: Microsoft (R) Build Engine version 4.8.3752.0 [Microsoft .NET Framework, version 4.0.30319.42000] Copyright (C) Microsoft Corporation. All rights reserved.4.8.3752.0
OS info: Windows 10 1903. OS build: 18362.418
If applicable, version of the tool that invokes MSBuild (Visual Studio, dotnet CLI, etc):
Visual Studio v16.3.8 dotnet --info output:
.NET Core SDK (reflecting any global.json): Version: 3.0.100 Commit: 04339c3a26
Runtime Environment: OS Name: Windows OS Version: 10.0.18362 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\3.0.100\
Host (useful for support): Version: 3.0.0 Commit: 7d57652f33
.NET Core SDKs installed: 1.1.13 [C:\Program Files\dotnet\sdk] 2.1.202 [C:\Program Files\dotnet\sdk] 2.1.505 [C:\Program Files\dotnet\sdk] 2.1.602 [C:\Program Files\dotnet\sdk] 2.2.105 [C:\Program Files\dotnet\sdk] 2.2.202 [C:\Program Files\dotnet\sdk] 3.0.100 [C:\Program Files\dotnet\sdk]
All .net Standard projects are build against v2.0