CommunityToolkit / CommunityToolkit/Labs-Windows

Lack of Designer/Code assistance from VS with samples

Open
#192 5 comments 0 reactions 0 assignees View on GitHub
bug :bug: dev loop ➰ templating Uno
Dominant language
C#
Stars
482
Forks
89
PR merge metrics
No merged PRs in 30d

Description

I noticed we're getting proper tooling support in the Test shared project, but not in the sample one.

I think this is because we're using a shared project for the tests, but we're using some sort of assembly for the samples?

We should investigate switching to use the same shared project approach for the samples that we're doing with the tests.

This should hopefully give us better tooling support when working with samples which will be important.

You can see the difference by opening up an Experiment (or the ProjectTemplate) and opening up a XAML file in the test project (where you should see the platform UWP/WinAppSDK drop-down in the top-left) and where you should get intellisense in the XAML. If by contrast you open up a XAML file in the sample project, you get neither and just the XML tree in the dropdown or 'miscellaneous files'.

@Arlodotexe have you see this too? I think this is an artifact of just when we set things up initially vs. what we learned later?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.