VSCode Insiders and RC3
See original GitHub issueMoved from VSCode repo b/c they said so…
VSCode Version:1.1.1-Insider
OS Version: Mac 10.10.5
Steps to Reproduce:
- Upgrade to RC2 from RC1-Updatesomething, using the instructions provided for .Net Core
- Upgrade VSCode, see lots of log messages about how it’s installing RC3 … which I don’t get, given that I just installed RC2 - did I miss the memo about Insiders using RC3 when RC2 comes out? But then, clicking on the release notes, leads me to 1.2.0 release notes, for May 2016, and looks like an empty template…And finally, it looks like 10.10.x64 is getting left behind…and I must have not seen it, because the logs are saying that “The project does not list one of ‘osx.10.10-x64’ in the ‘runtimes’ section.” And it suggests that I run dotnet restore, which I do, but then it downloads rc-1 stuff, which I no longer want…Actually, here’s the full set of errors which came at the end:
Error: Can not find runtime target for framework ‘DNXCore,Version=v5.0’ compatible with one of the target runtimes: ‘osx.10.10-x64’. Possible causes:
- The project has not been restored or restore failed - run dotnet restore
- The project does not list one of ‘osx.10.10-x64’ in the ‘runtimes’ section. Error:
System.InvalidOperationException: Can not find runtime target for framework ‘DNXCore,Version=v5.0’ compatible with one of the target runtimes: ‘osx.10.10-x64’. Possible causes:
- The project has not been restored or restore failed - run dotnet restore
- The project does not list one of ‘osx.10.10-x64’ in the ‘runtimes’ section. at Microsoft.DotNet.ProjectModel.BuildWorkspace.GetRuntimeContext(ProjectContext context, IEnumerable1 runtimeIdentifiers) at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext() at System.Collections.Generic.List1…ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToListTSource at Microsoft.DotNet.Tools.Publish.PublishCommand.TryPrepareForPublish() at Microsoft.DotNet.Tools.Publish.PublishCommand.<>c__DisplayClass0_0.b__0() at Microsoft.DotNet.Cli.CommandLine.CommandLineApplication.Execute(String[] args) at Microsoft.DotNet.Tools.Publish.PublishCommand.Run(String[] args) dotnet exited with error code 1 Error while installing .NET Core Debugger.
So lots going on here.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Download Visual Studio Code Insiders
For early adopters, you can get the latest release of VS Code each day with the Insiders Build. Available on Mac, Linux and...
Read more >Introducing the Insiders Build - Visual Studio Code
The features included in the Insiders build is tracked in our iteration plans. Feel free to communicate your thoughts, ideas and bug reports...
Read more >Evolution of the Insiders Build - Visual Studio Code
Today over five thousand developers use the Visual Studio Code Insiders Build for early access to new features and to validate bug fixes....
Read more >Remote Development FAQ - Visual Studio Code
Remote Development FAQ. This article covers frequently asked questions for each of the Visual Studio Code Remote Development extensions.
Read more >Settings Sync in Visual Studio Code
You can sync your Insiders with Stable by selecting the Stable sync service while turning on Settings Sync. This option is only available...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry – Function+F1 is what I meant (at least, that’s what works on my MacBook Pro).
I don’t understand your reference to RC 3 either. I wonder if it’s just a typo somewhere. Where are you seeing that?
I’m glad you were able to get the latest C# extension. Yes, you will need to move your project.json forward to continue development.
Thanks for the request to add the version to the OmniSharp log. This has been on my personal TODO list for a long while but I keep forgetting to do it. 😄 Since you mentioned it, I went ahead and filed #346 to track the work.
Do let me know if you have any more issues.
By the way, I would think the Omnisharp log would want to list at least once what version it is…