vscode-csharp: xproj ignored. CodeLens don't show References, Find All References don't work
Environment data
dotnet --info
output:
.NET Command Line Tools (1.0.0-preview3-003805)
Product Information: Version: 1.0.0-preview3-003805 Commit SHA-1 hash: edf2fc1f53
Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64
VS Code version: 1.7.1 C# Extension version: 1.5.2
Steps to reproduce
Create solution with VS 2015 (with last Core updates). Works fine. Open solution folder in VSCode - CodeLens don’t show References, Find All References don’t work.
https://cloud.githubusercontent.com/assets/1697801/20385121/31689772-acc7-11e6-965a-3f00b0e07869.jpg
OmniSharp log
Starting OmniSharp server at 18.11.2016, 12:03:36 Target: c:\NewProject\New\LombardService
OmniSharp server started Path: C:\Users\WaSh.vscode\extensions\ms-vscode.csharp-1.5.2\bin\omnisharp\OmniSharp.exe PID: 7108
OmniSharp: -s c:\NewProject\New\LombardService --hostPID 11100 --stdio DotNet:enablePackageRestore=false --encoding utf-8 [INFORMATION:OmniSharp.Startup] Omnisharp server running using Stdio at location ‘c:\NewProject\New\LombardService’ on host 11100. [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Initializing in c:\NewProject\New\LombardService [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Auto package restore: False [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Update workspace context [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Resolving projects references [INFORMATION:OmniSharp#MSBuild] Detecting projects in ‘c:\NewProject\New\LombardService\LombardServiceNew.sln’. [WARNING:OmniSharp#MSBuild] Skipped unsupported project type ‘src\LombardService.Data\LombardService.Data.xproj’ [WARNING:OmniSharp#MSBuild] Skipped unsupported project type ‘src\LombardService.Services\LombardService.Services.xproj’ [WARNING:OmniSharp#MSBuild] Skipped unsupported project type ‘tests\LombardService.Services.Tests\LombardService.Services.Tests.xproj’ [INFORMATION:OmniSharp.Startup] Configuration finished.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 20 (14 by maintainers)
I’ve created a v1.6-beta2 release of the C# extension that contains this fix, among others. See this page for information on installing beta releases