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

Windows only - OmniSharp does not provide IntelliSense for strong named assemblies #6

Closed
chrisdias opened this issue Nov 13, 2015 · 1 comment
Closed

Windows only - OmniSharp does not provide IntelliSense for strong named assemblies #6

chrisdias opened this issue Nov 13, 2015 · 1 comment
Assignees
@jrieken
Labels
bug Issue identified by VS Code Team member as probable bug on-testplan upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Backlog

Comments

@chrisdias
Copy link
Member

upgrade to rc1 dnx/runtime

git clone https://github.com/natemcmaster/test-vscode-strong-name
cd test-vscode-strong-name
dnu restore
code .

pick the Test project.json

result => "Internal Class InternalClass is not accessible..." error.

Works on OSX
@chrisdias chrisdias added the bug Issue identified by VS Code Team member as probable bug label Nov 13, 2015
@chrisdias chrisdias modified the milestones: 0.10.0, 0.10.1, 0.11.0 Nov 13, 2015
@chrisdias
Copy link
Member Author

In general IntelliSense works for RC1 of ASP.NET v5. It appears to only fail in this scenario and feedback from the ASP.NET team suggests this is not a blocker for 0.10.1.

@jrieken jrieken added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Dec 2, 2015
@jrieken jrieken added the c# label Dec 14, 2015
@jrieken jrieken modified the milestones: Backlog, Dec 2015 Dec 14, 2015
@jrieken jrieken closed this as completed Jan 20, 2016
@johnf76 johnf76 mentioned this issue Jun 2, 2016
Closed
@jrieken jrieken mentioned this issue Aug 8, 2016
Closed
@JohnGalt1717 JohnGalt1717 mentioned this issue Mar 9, 2017
Closed
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jrieken jrieken

Labels
bug Issue identified by VS Code Team member as probable bug on-testplan upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@chrisdias @jrieken @VSCodeTriageBot