You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result of creating a number of new experiments and copying over existing code from the toolkit, I propose the following changes:
Rename the template from "Community Toolkit Labs Project Template" to "Community Toolkit Labs Experiment"
Include a reference to the default sample namespace in the example test class.
Include more namespaces (including Windows./Microsoft. options) in the example test class.
Include something (a readme?) in the generated solution to explain the structure of the solution and where to start looking for things to change/edit.
Reference the new sample project in the test projects
Add InternalsVisibleTo references in the generated code to all test projects. The local ones and the "all" solution. This is because lots of the existing tests in the main toolkit rely on this approach and doing this is going to be simpler than setting rules about not using internals in experiments as these would need to be changed when promoting from labs.
As a result of creating a number of new experiments and copying over existing code from the toolkit, I propose the following changes:
InternalsVisibleToreferences in the generated code to all test projects. The local ones and the "all" solution. This is because lots of the existing tests in the main toolkit rely on this approach and doing this is going to be simpler than setting rules about not using internals in experiments as these would need to be changed when promoting from labs.