Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should internal classes be made public with ComVisible(false) attribute? #38

Closed
retailcoder opened this issue Nov 14, 2014 · 2 comments
Closed

Should internal classes be made public with ComVisible(false) attribute? #38

retailcoder opened this issue Nov 14, 2014 · 2 comments
Labels
discussion

Comments

@retailcoder
Copy link
Member

Writing unit tests will be easier with public classes.
@rubberduck203
Copy link
Member

Yes. We should also consider explicitly registering only the items we want ComVisible and discontinue the use of the project wide build option "Make com visible". It makes a mess of the registry.

@retailcoder
Copy link
Member Author

Agreed.

@retailcoder retailcoder mentioned this issue Nov 14, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rubberduck203 @retailcoder