Close out these issues because of these reasons (part 2 included) :

[mominshaikhdevs]

@RDMacLachlan

Issues	Issues Descriptions	Reasons for Closing
1	#128	AppInstaller is present in every Win11. so, no need.
2	#986	UWP/CoreWindows are not supported by WASDK.
3	#829	same as 2.
4	#1228	same as 2.
5	#1488	same as 2.
7	#1646	completed.
8	#1833	AppInstaller Issue / Out of Scope of this repo.
9	#1991	same as 2.
10	#2006	Close and convert it into a discussion.
11	#2639	completed except M.S.AD.GetForUnpackaged() this old issue should be closed and a new issue should be filed.
12	#2908	Out of scope of this repo.
13	#2981	BuildTools.MSIX in 1.8
14	#3037	No Repro
15	#3242	completed by #5256 (comment)
16	#3298	completed.
17	#3338	completed.
18	#3556	completed.
19	#3659	.NET Projection Issue. Transfer it over to C#/WinRT repo.
20	#3816	dup of #3595
21	#4252	completed.
22	#4369	completed.
23	#4568	completed.
24	#4625	No Repro.
25	#4791	I believe completed by the subsequent PRs of @DrusTheAxe.
26	#4839	completed
27	#5139	BuildTools.MSIX exists.
28	#5199	Fixed in newer Windows builds.

[RDMacLachlan]

Wow! Thank you @mominshaikhdevs this is very helpful! I'll review and close them :-) thank you!!

[mominshaikhdevs]

Part 2 :

---

Issues	Issues Descriptions	Reasons for Closing
29	#4577	No Repro.
30	#5071	Completed.
31	#4932	same as 27.
32	#4889	same as 30.
33	#4829	same as 10.
34	#4498	WindowsAppSDK-VersionInfo.h exists.
35	#4460	same as 28.
36	#4340	same as 28.
37	https://github.com/microsoft/WindowsAppSDK/issues/4364	same as 19.
38	#4387	Completed.
39	#4390	Completed.
40	#3887	same as 19.
41	#3901	same as 10.
42	#4068	same as 2.
43	#4054	same as 10.
44	#4046	same as 2.
45	#3928	same as 28.
46	#3957	same as 19.
47	#4201	M.W.AM.UBGTask exists.
48	#3815	dup of #3595
49	#4006	same as 28.
50	#3764	completed.
51	#3528	same as 10.
52	#3718	completed by #4603.
53	#3450	same as 10.
54	#3390	same as 19.
55	#3369	same as 28.
56	#5199	same as 28.
57	#3151	completed by #1762.
58	#3133	same as 28.
59	#2922	Completed.
60	#2981	BuildTools.MSIX exists.
61	#3047	same as 10.
62	#3078	Completed.
63	#3106	dup of #2918.
64	#3110	Completed.
65	#2965	same as 28.
66	#2943	dup of #41.
67	#2425	Completed.
68	#2469	Completed.
69	#2492	No Repro.
70	#2398	AppWindowTitlebar exists.
71	#2343	completed by #2295.
72	#1883	dup of #3242.
73	#1443	same as 19.
74	#1480	same as 10.
75	#1487	same as 2.
76	#1528	completed.
77	#1609	dup of #4829.
78	#1660	completed.
79	#1664	same as 13.
80	#1750	same as 12.
81	#1769	same as 13.
82	#1776	same as 10.
83	#1643	dup of #41.
84	#1034	completed.
85	#1063	same as 2.
86	#1098	dup of #95.
87	#1151	WindowsAppSDK MetaPackages exist.
88	#1240	WASDK-Installer.exe exists.
89	#1359	same as 13.
90	#1405	Widgets exist.
91	#713	same as 10.
92	#833	same as 2.
93	#2286	Completed.
94	#711	dup of #713.
95	#27	same as 28.
96	#88	same as 10.

[riverar]

@RDMacLachlan I have concerns about some of these proposed actions. If Microsoft is seeking community assistance with issue triage, I'd suggest announcing this formally or partnering with established community members and MVPs who have deeper context on these older issues.

I'm particularly concerned about migrating issues to discussions, as this often results in reduced visibility and engagement. For many of these issues, discussions may not be the appropriate venue and could stall progress rather than facilitate it.

[mominshaikhdevs]

...or partnering with established community members and MVPs who have deeper context on these older issues.

since when, github issues became tied to those "established community members and MVPs" only? "Community can't participate or give their thoughts", is that documented somewhere? Am I missing something?

... I'm particularly concerned about migrating issues to discussions...

It's nothing new. It happend in the past. It's been happening already. 💁

[sylveon]

And everytime it's happened, it died. Discussions is where issues go to die. We shouldn't encourage it.

[RDMacLachlan]

Hi @riverar,
My development team and I have been evaluating the list of GitHub Issues and the proposed actions provided by @mominshaikhdevs. Based on our evaluation, the team has either chosen to close the Issue or leave it in its current state.

I appreciate all feedback and support from the community. If you have any concerns about the items listed, kindly contribute to this discussion.