-
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.6-Beta5 (and other versions) incompat with old upgraded project #1050
Comments
@mcmonkey4eva: I have a couple of questions:
|
Note that I couldn't reproduce the issue with your project file. I got the following in my OmniSharp log.
I'll try reproducing the issue by starting with a web project created with Preview2 and then migrating it to Preview 5. |
No dice. 😞 I did the following: preview2-3131: Then, I performed a |
Definitely let me know which versions of Visual Studio you have installed on this machine (if any) when you get a chance. |
OK. I just took a look at the OmniSharp bits installing in 1.6-beta5, and it looks like it actually has the wrong binaries. My original fix does fix this issue, but the binary does not include it. This was probably just an error in publishing. I should have it fixed soon. |
I pushed 1.6-beta6 which should fix the problem for real this time. |
I verified that my fix is properly in 1.6-beta6 this time. |
Woo! That did it! Thanks! :) |
Awesome. |
( Moved from https://github.com/dotnet/cli/issues/4999 )
The error has moved a few line numbers but otherwise persists...
Path: C:\Users\mcmonkey\.vscode\extensions\ms-vscode.csharp-1.6.0-beta5\bin\omnisharp\OmniSharp.exe
For a bit of background, the project was started on a public release of .NET Core CLI (I believe 1.0.0 Preview 2-1), with a
project.json
file, then upgraded to .NET Core CLI 1.0.0 Preview 5 to.csproj
viadotnet migrate
.It's an ASP.NET MVC setup. the Csproj file is posted for the original issue at http://pastebin.com/VBxaXzwA
OS is a standard and regularly updated installation of Windows 10.
dotnet --info
:The text was updated successfully, but these errors were encountered: