-
Notifications
You must be signed in to change notification settings - Fork 676
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
1.13.0-beta4 fails to resolve output dll #1821
Comments
Since the error is coming through Xamarin's Android task, do you need to build first or do anything special? |
@DustinCampbell project is already built, and I don't know about any special command 😐 |
Does this assembly exist anywhere?
|
Very much so :) |
Hmmm... I wonder if the problem is that OmniSharp is simply defaulting to "Debug". Could you place the following {
"MsBuild": {
"Configuration": "Release"
}
} |
Is there any chance you could share the project? I'd love to get this under the debugger and see what's happening. |
Wish I could, and I cannot recreate the issue :( |
@Casz: I assume that this issue is still reproducible for you with the latest version of C# for VS Code (1.13) that was released a couple of days ago? |
@DustinCampbell I reproduce this issue with C# extension 1.13.0. I think this issue is caused by 2 msbuild instances, but the C# plugin doesn't locate right one.
I want to know how can i select the second msbuild instance(StandAlone 15.0 - "C:\Users\Administrator.vscode\extensions\ms-vscode.csharp-1.13.0.omnisharp\msbuild\15.0\Bin") ? |
@DustinCampbell Additionally, i also have installed vs2017 and C# module. |
@DFVSQY THANKY YOU for finding a way to reproduce 🚀 |
A lot has changed with O# project loading since this issue was opened. If this is still a problem, please open a new issue at https://github.com/OmniSharp/omnisharp-roslyn |
Environment data
dotnet --info
output:VS Code version: 1.17.2
C# Extension version: C# 1.13.0-beta4
Steps to reproduce
tbh, I dno 😐
Expected behavior
resolve output file correctly
Actual behavior
The text was updated successfully, but these errors were encountered: