Incremental Loading Behavior for ItemsView #600
Conversation
|
I've tried to run ApplyXamlStyling.ps1 -MainAnd it said no file to style. Why the workflow still fails |
|
@Poker-sang it's this file:
I'm not sure why the tool isn't fixing it locally for you, I wonder if we have an issue with the script when run against forks... hmm What does running It could also maybe be an issue if folks don't have their remote labeled You should just be able to run |
| MultiTarget is a custom property that indicates which target a project is designed to be built for / run on. | ||
| Used to create project references, generate solution files, enable/disable TargetFrameworks, and build nuget packages. | ||
| --> | ||
| <MultiTarget>uwp;wasdk;wpf;wasm;linuxgtk;macos;ios;android;</MultiTarget> |
There was a problem hiding this comment.
Since this is only good for WinUI 3, remove uwp here. @Arlodotexe that should exclude it from making an entire UWP package for Uno too, eh? Then we wouldn't need the #if WINAPPSDK conditional, right?
There was a problem hiding this comment.
Yes this feature only works for wasdk. But sorry that I'm not familiar with tooling project, so don't know how exactly i should do. I hope you can help me fix this❤️thanks
There was a problem hiding this comment.
@Arlodotexe maybe something we can lend a quick hand with this after the long weekend here?
There was a problem hiding this comment.
The MultiTarget declarations are deployable target declarations. Uno-powered platforms support both WinUI 2/3 while UWP supports only WinUI 2 and Wasdk supports only WinUI 3.
If certain code within a component only works under certain configurations, we use compilations conditionals such as WINUI2, WINUI3 and HAS_UNO. The WINAPPSDK const is the legacy version of the WINUI3 const. See here for the full list.
Thanks, this works |
|
Also revert |
Poker-sang
force-pushed
the
itemsview-behaviors
branch
from
a9db5e9 to
a8059fa
Compare
Includes
NeedMoreItemTriggerBehaviorandLoadMoreItemBehavior