Porting Behaviors

[Arlodotexe]

This PR ports Behaviors from the old WCT repo. Closes #7.

Prerequisite PR CommunityToolkit/Tooling-Windows-Submodule#46

[Arlodotexe]

After more testing, KeyDownTriggerBehavior doesn't work on WASM. Will investigate more tomorrow.

[michael-hawker]

Rebased on top of main and removed commits for the tooling submodule updates.

[michael-hawker]

WinUI 2 fail from .NET Native
WinUI 3 from:

       "D:\a\Windows\Windows\CommunityToolkit.AllComponents.sln" (default target) (1:2) ->
       "D:\a\Windows\Windows\tooling\ProjectHeads\AllComponents\Tests.WinAppSdk\CommunityToolkit.Tests.WinAppSdk.csproj" (default target) (20:6) ->
       "D:\a\Windows\Windows\components\Extensions\src\CommunityToolkit.WinUI.Extensions.csproj" (GetTargetPathWithTargetPlatformMoniker target) (8:259) ->
         D:\a\Windows\Windows\components\Extensions\src\CommunityToolkit.WinUI.Extensions.csproj : error MSB4057: The target "GetTargetPathWithTargetPlatformMoniker" does not exist in the project.

Very weird. 🤔 Could it be dotnet/msbuild#4303?

[michael-hawker]

Going to try changing back the path thing just to try... otherwise I'm not really sure what's different about this PR...

[michael-hawker]

@Arlodotexe pretty sure that was is... WinUI 3 build just succeeded. Seems like docs are wrong about the trailing slash or something...? Maybe good for us to keep breaking up PRs our that make other miscellaneous changes.

[Arlodotexe]

@Arlodotexe pretty sure that was is... WinUI 3 build just succeeded. Seems like docs are wrong about the trailing slash or something...? Maybe good for us to keep breaking up PRs our that make other miscellaneous changes.

That's... really odd. I've had issues in Labs in the past where MSBuildThisFileDirectory (the value of RepositoryDirectory) added a trailing slash and caused issues with other tooling. In the future, if we start hitting those problems again, MSBuild provides a few property methods that should help.

Moving forward then, thanks for the hand @michael-hawker!

[michael-hawker]

Good with merging, but we should add tasklist line-items to follow-up and investigate on the main tracking issue:

• AutoSelectBehavior not working on WinAppSDK
• AutoSelectBehavior not working when clicking in/on the textbox, only with keyboard focus (I think the new platform styles don't show selection when the control doesn't have focus, so this may be related compared to how it used to work?)
• Bit confused by FocusBehavior and what it enables, maybe we can improve docs/samples later
• The KeyDownTriggerBehavior not working on WASM as you mentioned
• Doesn't look like the IsAlwaysOn properly unregisters for the ViewportBehavior on WASM