I have a workspace with several unrelated folders in it. I don't get any C# code checks (errors marked red and such). I followed this and checked the output of the OmniSharp log which only contained info about the topmost project in my workspace. This issue is addressed here as well, and I tried following its solution saying that one just needs to switch the project:
Unfortunately, my VScode has neither a project selector in the bottom-right of the status bar nor a project picker at the top:
Or maybe it has, but I don't see it anywhere.
How do I get (any of those) project pickers for my VS code?
How do I tell OmniSharp to work on a project/solution of my choice?
I have VS Code version 1.63.2 according to Help -> About.
Press Ctrl + Shift + P in VS Code.
Type “OmniSharp: Select Project” and press Return.
Select the top level sln or csproj
Related
In sublime, when I drag a new folder into the editor, it gets added at the bottom of the list in the sidebar, but in VS Code, the old project is removed from the list on only the current project is active.
Is there any way to make VS Code sidebar hold the old projects as sublime did? (PS: I am new to VS Code)
Here is a comparison of Sublime sidebar and VS Code sidebar.
EDIT: I have tried the VS Code Insiders edition, The add to workspace option kind of works, but is not the exact solution of what I was looking for. Because even if you add multiple folders to the workspace, the next time you drag and drop a folder in VS Code, The workspace will get replaced with the new folder which you opened. I want that old folder to remain in the sidebar, and the newer folder to open below it like in sublime (see the image for reference).
Use Insiders version of vscode. There was introduces a feature called multi-root workspace. In nutshell: you can open multiple folders in 1 vscode window (drag-n-drop supported too).
I just started using Visual Studio Code Version 1.15.1 and for some reason, after closing all the folders in the navigation explorer side bar, I cannot get it back to display the folder structure and files in the project, even after closing and reopening. The files and folders are available and I can see them fine in OSX Sierra. Also the VS code window title shows the name of the project.
You can get it back by right clicking on the sidebar "Explorer" header, and selecting "Folders". See the gif here: https://github.com/Microsoft/vscode/issues/32962#issuecomment-324866098
This has confused several people so we've decided to remove the ability to hide the "Folders" view. Continuing discussion on the general UI is here: https://github.com/Microsoft/vscode/issues/31485
I would like to have an additional feature in Visual Studio Code - essentially the "Scope to This" from the full Visual Studio Solution Explorer.
It is basically a context menu (right click) entry in the File Explorer of Visual Studio Code - which then should limit which files and folders are displayed.
Is such a thing possible with a Visual Studio Code Extension?
I never built an extension for VS Code before and would like to know if this is even possible or if I would just waste my time.
According to the API docs, there is no way to filter visible files in the Explorer like it can usually be done with the files.exclude setting. However, it is possible to open another folder with the workspace.openFolder complex command. This will probably also close all opened editors, and forget about the original workspace root path.
Your extension would need to remember the initial root path and opened editors to undo this "Scope to This" menu, and reopening everything every time could cause quite some lag.
You can't customize the normal explorer view.
However, you can do something like this with custom views. It allows you to create a new explorer view that can list what you want and behave as you want.
For an example implementation, check the vscode-code-outline.
If you can add a context menu entry separately too.
I would like to have a certain folder in the Project Explorer expand automatically upon opening the project (or starting Eclipse with the project already open).
When working on multiple projects, you find yourself closing and opening projects a lot, and closing all relevant editors (Ctrl + Shift + w), so the editor link as commented by Torsten is not the solution I am looking for.
Pressing asterisc (*) expands all folders. However, I would like this (1) to happen automatically, and more importantly (2) only expand a certain (sub)folder.
Is this possible?
Try Shift+numpad_multiply for exapanding every file under a package/folder and Ctrl+Shift+numpad_divide for collapsing a project. I think this works better on Navigator for a big project because when I tried it in my project explorer, I ended up crashing eclipse.
I have what appears to be a very annoying problem. When compiling a project in Eclipse, I see no Console that shows the invocation of the Java compiler and the build results (as in NetBeans).
If I, for instance, import an existing project into Eclipse and invoke Project->Build Project, is there a view that will show me results of the compilation? While I know that my project contains a number of files that have errors, invoking Build Project shows no visual result/progress of the compilation. It does not show the list of errors so that I can quickly jump to them.
I'm aware that there is a "Problems" view, which shows a list of problems (and not just compiler errors) in all projects and not the particular project that I am working with, which makes it very inconvenient to locate and jump to source of the problem.
You can configure the problem view to show only problems in the current project:
Click on the small triangle at the far right of the view.
In the popup menu, select "Configure Contents..."
Select each item in the "Configurations" list and click on "Scope: On any element in the same project"
If you want to see the compiler working, you need open the "Progress" view.
Since Eclipse JDT provides its own built-in Java compiler, you generally do not see the invocation of Java Compiler.
The built-in Java compiler is tightly integrated with Eclipse and JDT, and provides the source indexing that enables powerful IDE features such as refactoring and quick fix.
Plus, it enables incremental build in background after each file modification, hence no visible "java" invocation.
You can replace/complete the java compiler with a javac` call of your own:
For instance, Using Alcatel-Lucent nmake with Eclipse JDT does precisely that, and uses a configuration launcher (which you can instruct to show a console):
You will need to add that special builder in the "builder" section of your project.
Do not forget you can create many "Problem view", and set one of them to show only problems for your current project.
Select: "on any element in same project"
Goto Windows->Show View->Console
or
Alt+Shift+Q,C
Console appears in tab with Problem view
Your question contains a couple of assumptions that you might want to re-think.
It does not show the list of errors so that I can quickly jump to them.
Errors are flagged in the edit window while you are editing. You can fix them on the spot, without having to "jump" anywhere.
If you drop an entire source file into your project, you may not be in an edit window on that file. (And, of course, that's not standard Eclipse usage.) The simplest way I know do deal with that is simply to "Refresh" the project and look in the Package Explorer view to see whether there are any errors detected (which will happen immediately if you "refresh" a file into a source folder). Double-click on any files which show an error icon and look at the right-hand side of the edit window to see exactly where the errors are.
I'm aware that there is a "Problems" view, which shows a list of problems (and not just compiler errors) in all projects and not the particular project that I am working with...
Unless you are using multiple projects, with inter-project dependencies, I find it useful to close all but the current project on which I'm working. Then the "Problems" view is specific to the current context.
Finally, I'd recommend looking at the Mylin "getting started" page for other hints on how Eclipse can help you focus on the current task.