Conversation
|
paging @michael-hawker @Arlodotexe for comments on the above open questions. |
Probably not, especially if we aren't using WinUI there. @michael-hawker do we want to just remove the |
|
In the netstandard version, we'll also want to use a normal .NET 6 MSTest project, rather than the full UWP/WinAppSDK UI test projects currently used. |
|
Discussed during our meeting, we're going to open a new issue to track a .NET Standard option, most likely as a whole separate template, but table that for now. Matt's going to investigate the |
|
Based on the error message, looks like something was missed from being excluded (e.g. looking for classical in backed). |
|
Removing the creation of two versions of the experiments as this is only useful if also combining them into the "All" solution. |
|
Yeah, next week I'll look into seeing if we can split out the workflows and use the path filtering so we only run the template/experiment job when the common/template folders have changes. |
|
Failure looks to be due to the Uno SourceGenerators not seeing the files linked from the "..*-backed" and "..*-classic" directories. |
|
Bubbling up the error from the CI here: |
|
Closing PR as stale. We'll use the code here an example, but the changes are so diverged by now (not even the same repo) that we'll need to redo it. |
For CommunityToolkit/Tooling-Windows-Submodule#65
What this does:
--backedis included when callingdotnet new labexpthe generated experiment will include a control that uses a style with a code-behind file, so that it's possible to usex:Bind.This looks to be blocked by a Uno issue and so may need #174
Also, for this to be useful, it also needs #180 to be fixed.