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.

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

CodeCompletion and internal classes #7771

Closed
Serg2DFX opened this issue Jan 4, 2016 · 3 comments
Closed

CodeCompletion and internal classes #7771

Serg2DFX opened this issue Jan 4, 2016 · 3 comments
Labels
Area-IDE Feature Request Resolution-Duplicate The described behavior is tracked in another issue

Comments

@Serg2DFX
Copy link

Serg2DFX commented Jan 4, 2016

Hello, guys!
It seems strange to use internal classes in "Microsoft.CodeAnalisys.Completion".
It seems to me that this functionality should be open.

@davkean
Copy link
Member

davkean commented Jan 8, 2016

@Serg2DFX By default we don't automatically make all types public.

What are you trying to do with these APIs? This will help us prioritize, and help us design something appropriate for your situation.

@Serg2DFX
Copy link
Author

Serg2DFX commented Jan 8, 2016

I saw an example of autocompletion in c # with Roslyn (https://github.com/aelij/roslynpad).
I replaced the nested assembly to nuget packages. But found that the changed classes visibility.

At the moment I am looking at two ways to solve:

  1. Make a fork of the project and change the visibility roslyn have used classes.
  2. Make a fork and add the assembly attribute [assembly: InternalsVisibleTo (...

Maybe it's not the best solution.

@Pilchie
Copy link
Member

Pilchie commented Jan 11, 2016

Dupe of #3538.

@Pilchie Pilchie closed this as completed Jan 11, 2016
@Pilchie Pilchie added the Resolution-Duplicate The described behavior is tracked in another issue label Jan 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Feature Request Resolution-Duplicate The described behavior is tracked in another issue
Projects
None yet
Development

No branches or pull requests

4 participants