Skip to content
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

Unable to create app package #3544

Closed
aquinn39 opened this issue Dec 6, 2021 · 8 comments
Closed

Unable to create app package #3544

aquinn39 opened this issue Dec 6, 2021 · 8 comments

Comments

@aquinn39
Copy link

aquinn39 commented Dec 6, 2021

After following the 'Package the app' section of the tutorial here: https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/host-standard-control-with-xaml-islands, I am unable to create an app package for the app due to the following errors:

• Validation error. error 80080204: App manifest validation error: Line 217, Column 27, Reason: The field "[local-name()='Extensions']/[local-name()='Extension']/[local-name()='InProcessServer']/[local-name()='ActivatableClass']" with value "Microsoft.Toolkit.Win32.UI.XamlHost.XamlApplication" must only be declared once. A duplicate exists on Line 42, Column 27.
• PRI175: 0x80073b0f - Processing Resources failed with error: Duplicate Entry.
• PRI222: 0x80073b0f - Unspecified error occurred.

I have added a reference to both the WPF app and the UWP app to the app package as per the tutorial as I would like to upload the app to the Microsoft Store. I am following this tutorial as I would like to use WinUI 2 with XAMLHost, which works fine when the WPF app is built outside of the package or if built inside the package without referencing the UWP app in the package.

App I am using is a new .NET Core 3.1 app and I have followed all of the requirements in the tutorial. There are no other packages or files that have been added.

It seems like this may have been broken in an update to Visual Studio as it used to work I believe.

I am using Visual Studio 2022 17.0.2.
I also tried using Visual Studio 2019 16.11.5.
Same issues with both.

Also reported this issue on Visual Studio Feedback here: https://developercommunity.visualstudio.com/t/Unable-to-create-Store-app-package/1668742 and Feedback Hub here: https://aka.ms/AAhjfmc.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@aquinn39
Copy link
Author

aquinn39 commented Dec 8, 2021

I've downgraded to Visual Studio 2019 version 16.9.8 and this seems to have fixed all of the issues. I would much prefer to be able to use Visual Studio 2022 though or at least the latest version of 2019.

@stevewhims
Copy link
Member

Thanks, @aquinn39. I'm getting the same build error with VS 2022 17.1. I've reached out to the product team for info about this particular issue.

Meanwhile, I took a pass through the topic, because previously it was talking about VS 2019. Since the steps work (apart from the issue you're seeing) for VS 2022, I updated the topic and just generally tidied it up and simplified it a little.

I'll get back to you when I get more info.

Thanks!
-Steve

@aquinn39
Copy link
Author

Hi @stevewhims,

Do you have any updates on this?
I'd really like to use Visual Studio 2022 for many projects that have this issue but am still stuck using 2019 as 2022 can't build them (I've checked on the latest version at the time of writing this, 17.1.5).

@stevewhims
Copy link
Member

Thanks, @aquinn39. I've reached out again for info. I'll keep you posted; sorry about the delay.

-Steve

@stevewhims
Copy link
Member

Thanks for the reminder. I've reached out again for info.

-Steve

@stevewhims
Copy link
Member

I've just made a small change to this topic (and 6 others like it). I added a note to draw attention to the support notice in the GitHub repo for the Windows Community Toolkit. All the relevant details are in that notice.

At the moment, it's not clear whether the problem is with the Windows Community Toolkit or with Visual Studio. At the same time, it's not clear that there are any changes that need to be made to the documentation in this topic. In light of all of that, and the age of this issue, I'm going to go ahead and close it. I'll be more than happy to reactivate it, and fix the topic, if anything concrete comes up that needs fixing.

Thanks!
-Steve

learn-build-service-prod bot added a commit that referenced this issue May 5, 2023
…c_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants