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
then the fluent assertion extensions and assertions class should not be generated in the unit test project that references that project, because the compiler will complain that the internal class is not accessible
The text was updated successfully, but these errors were encountered:
into the project with internal classes, but that is not a clean solution.
When someone has declared <InternalsVisibleTo ... /> and wants to assert the internal types, maybe a global attribute is necessary to indicate that.
Maybe something like
e.g. when there is
then the fluent assertion extensions and assertions class should not be generated in the unit test project that references that project, because the compiler will complain that the internal class is not accessible
The text was updated successfully, but these errors were encountered: