-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test projects don't support csproj, dependencies or multitarget preferences #101
Labels
Comments
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Jul 17, 2023
Fix test relying on it, see CommunityToolkit/Tooling-Windows-Submodule#101
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Jul 17, 2023
Fix test relying on it, see CommunityToolkit/Tooling-Windows-Submodule#101
We should probably just support |
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Jul 21, 2023
Fix test relying on it, see CommunityToolkit/Tooling-Windows-Submodule#101
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Aug 1, 2023
Fix test relying on it, see CommunityToolkit/Tooling-Windows-Submodule#101
Arlodotexe
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Oct 30, 2024
csproj support in tests would also enable MultiTarget support, which would allow us to disable running component tests on unsupported test heads and avoid the need or workarounds like this: CommunityToolkit/Labs-Windows@b3cf490 |
Arlodotexe
changed the title
Tests can't have extra dependencies
Test projects don't support csproj, dependencies or multitarget preferences
Oct 30, 2024
Arlodotexe
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Oct 30, 2024
Arlodotexe
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
Oct 31, 2024
20 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
For samples we allow adding extra dependencies that are needed to showcase things just in the samples (but not required by the base component).
However, we don't have this same setup for the tests.
For instance, in DataTable it doesn't required the HeaderedControls, but we'd like to test against them still.
Steps to reproduce
Expected behavior
Able to add framework specific dependencies for UWP/WASDK to a test project within a component.
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.
The text was updated successfully, but these errors were encountered: