Microsoft.Services.Store.SDK - Feedback Hub in WinUI3

[mvpete]

I am trying to follow this UWP article for launching feedback hub, but unable to resolve references. Is it possible to launch the feedback hub from a Win UI 3 application? I've installed the SDK, also tried NuGet packages with no luck. My app is C# .NET 6 application, on Windows 11, using Visual Studio 2022.

[castorix]

I am trying to follow this UWP article for launching feedback hub, but unable to resolve references. Is it possible to launch the feedback hub from a Win UI 3 application? I've installed the SDK, also tried NuGet packages with no luck. My app is C# .NET 6 application, on Windows 11, using Visual Studio 2022.

I could compile with CsWinRT package, with
<TargetFramework> net5.0-windows10.0.19041.0 </TargetFramework>
on Windows 10 21H1
But then it crashes at execution...
(even just with
Microsoft.Services.Store.Engagement.StoreServicesFeedbackLauncher.IsSupported())
(I added a Manifest for the minimum Windows 10 version but nothing changed...)

[mvpete]

I didn't even get it to compile... I looked at launching it with the feedback URI, which works... but it's not targeted at the specific app. Though, I've not done much research down that road.

[JoeTomkinson]

Looks as though the package just doesn't work on .NET 6 WinUI apps. I've had a bit of a dig around and although it doesn't look like there are any glaringly obvious package dependency issues on the face of it there must be as the project refuses to allow the referencing of the package.

[karter16]

Has there been any progress on this. The lack of availability of features for the Services.Store.SDK for WindowsAppSDK apps is pretty disappointing.

[mklemarczyk]

@DarranRowe Create a new WinUI 3 app, and add nuget package. You will see that Visual Studio does not recognize the namespace for class StoreServicesFeedbackLauncher.

<Project Sdk="Microsoft.NET.Sdk">
	<PropertyGroup>
		<OutputType>WinExe</OutputType>
		<TargetFramework>net8.0-windows10.0.22621</TargetFramework>
		<TargetPlatformMinVersion>10.0.17763.0</TargetPlatformMinVersion>
		<ApplicationIcon>Assets/WindowIcon.ico</ApplicationIcon>
		<ApplicationManifest>app.manifest</ApplicationManifest>
		<Platforms>x86;x64;ARM64</Platforms>
		<RuntimeIdentifiers>win-x86;win-x64;win-arm64</RuntimeIdentifiers>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>
		<UseWinUI>true</UseWinUI>
	</PropertyGroup>

App packaged with separate Msix project.

Steps to reproduce :

• Install Visual Studio 2022 with .NET 9.
• Create new project for WinUI 3.
• Add Store package <PackageReference Include="Microsoft.Services.Store.Engagement" Version="10.2307.3001" />
• try to compile with line : Microsoft.Services.Store.Engagement.StoreServicesFeedbackLauncher.IsSupported()

[DarranRowe]

@mklemarczyk

In that case it is understandable. There is no CsWinRT projection. This is also technically outside of the scope of this repo.

[mklemarczyk]

@DarranRowe it works with C# in scope of UWP. So what is missing now for WindowsAppSDK & WinUI3 ? Who should manage support for it ? Microsoft don't want to support own products and technologies anymore ?

[DarranRowe]

It works with C# in scope of UWP because that should be based on the .NET framework or .NET core. .NET 5 removed builtin support for WinRT, so nothing is missing from the Windows App SDK/WinUI 3, it is .NET which is missing everything.

This is the reason why the CsWinRT project exists, but the Store Services SDK team never added a projection to the Microsoft.Services.Store.Engagement package. So the team which are responsible for this would be the Store Services SDK team. Maybe you can go to the NuGet page and use contact owners there to try to get something done.

[mominshaikhdevs]

@Sergio0694 works in the Store team.