Problems with InternalsVisibleTo #441
Comments
|
Adding additional details highlighted in #446: We're testing these changes for three reasons:
The third reason is dismissed, CommunityToolkit/Tooling-Windows-Submodule#195 (comment) helped us verify that it was unrelated, and the fix offered by Mano and yourself @Sergio0694 double confirms that. The first two are still a possible concern. If we can verify that the use of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Worth noting our use of
InternalsVisibleToare using or being used by same set of components that keep appearing in these issues-- Behaviors, Animations, Media and Extensions.If our use of
InternalsVisibleTois indeed related to our AoT issues on Wasdk as well as what we've seen here regarding transient dependencies, it might be highlighting a deeper issue with how we've set up these libraries.We might want to go through and see if we can remove the need for these
InternalsVisibleTo, it looks like at least a few are just to avoid helper duplication. If it fixes any of the issues we've listed throughout this ticket, we've narrowed the scope of our search down considerably.Originally posted by @Arlodotexe in #169 (comment)
The text was updated successfully, but these errors were encountered: