-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppServices isn't updating in NuGet feed #623
Comments
Fixed the build in CommunityToolkit/Tooling-Windows-Submodule@3e178bc. However packaging now fails. Progress? |
The next error message here is:
To repro the error, run the build command normally in Labs: ./tooling/Build-Toolkit-Components.ps1 -MultiTargets all -Components AppServices -ExcludeMultiTargets wasdk -WinUIMajorVersion 2 -NupkgOutput ./ -Release -bl Seems like the issue stems from this line:
It's worth noting the actual content of the Given this, there are two possible reasons why this declaration breaks:
The second one is our best lead here. If you declare ./tooling/Build-Toolkit-Components.ps1 -MultiTargets all -Components AppServices -ExcludeMultiTargets wasdk -WinUIMajorVersion 2 -NupkgOutput ./ -Release -bl -AdditionalProperties @{ "Platform" = "x64" } @Sergio0694 This may be related to modern .NET support now being enabled for UWP on AppServices. We shouldn't have to declare this as a global property, I think. What do you recommend? |
Describe the bug
The latest update to our Labs NuGet feed saw a silent failure in the AppServices component, causing the component to not build or publish.
Steps to reproduce
Expected behavior
Component should have built and published.
Screenshots
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
CommunityToolkit.AppServices.msbuild.zip
Help us help you
Yes, I'd like to be assigned to work on this item.
The text was updated successfully, but these errors were encountered: