You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove test-side Resizetizer workaround once dotnet/maui#35575 ships #136
The library-mode testing pattern (PR #135) requires workarounds in the test project's TestingWorkarounds.targets because MAUI's Resizetizer and Windows PRI tooling don't propagate AdditionalProperties from ProjectReference when invoking targets on referenced projects.
Upstream fix
dotnet/maui#35575 fixes the Resizetizer issue. The fix is a single line: appending %(_ResizetizeCollectItemsProject.AdditionalProperties) to the Properties parameter in the GetMauiItems MSBuild call. The metadata already flows from Include="@(ProjectReference)" — it just wasn't being used.
What to do when the fix ships
Once the MAUI version containing #35575 is released:
Delete the _RemoveImportedAppResizetizerItems target from sample/test/DeviceTestingKitApp.AppTests/TestingWorkarounds.targets
Updatedocs/articles/testing-with-app-resources.md to remove the Resizetizer workaround from the drop-in targets template
Bump the minimum MAUI version in Directory.Packages.props (or document the minimum version needed)
What remains
The Windows PRI workaround (_FixWindowsPriForAppReference) is still needed — GetPriOutputs has the same issue but is in the Windows App SDK, not Resizetizer. A separate fix/issue is needed for that.
The app-side TestingWorkarounds.targets is always required — it's the mechanism that enables library mode, not a workaround.
Verified locally
Patching the NuGet cache with the 1-line fix and disabling the workaround:
Build: 0 errors, 0 warnings ✅
Tests: 10/10 pass ✅
AdditionalProperties only flows to the specific ProjectReference that has it ✅
Activity
Rewrite docs with drop-in targets and workaround explanation
Rewrite docs with drop-in targets and workaround explanation