I would like to know if anyone knows how to flatten the package structures in Visual Studio Code.
I used to have this in my IntelliJ IDE, but with VS Code I can't find a similar option. I am looking for any solution which could resolve this. Either changing settings or extensions if available.
This is supported since the 1.41 release (November 2019) and enabled by default. VSCode calls this feature "compact folders", and it can be disabled like this:
"explorer.compactFolders": false
(gif from the release notes)
For java the only way i found is using this extension
(it won't change the default file explorer, but you can fold that one and use this one instead).
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-dependency
or goto your VSCode->Extensions and search for "Java Dependency Viewer".
In VS Code v1.73.1 (latest as of this writing) folders are rendered in a compact form by default. To change this, go to File/Preferences/Settings/Features/Explorer and deselect Compact Folders.
Related
I have a C code (pretty old one) that I tried to run in VS17 and am getting this error:
The build tools for Intel C++ Compiler 17.0 (Platform Toolset = 'Intel C++ Compiler 17.0') cannot be found. To build using the Intel C++ Compiler 17.0 build tools, please install Intel C++ Compiler 17.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I am not including the code as it is old and big.
Can someone please suggest what the problem is?
It means your project configuration was done with an old version of Visual Studio.
I suggest you follow the VS suggestion: at the solution pane, right click on the project/solution and select 'retarget solution'. This will change your solution/project configuration to the current visual studio you use (2017).
As the project/solution files will be overwritten by the 'retarget' process, it worth copying the solution/project files (or even the entire solution
directory) before starting the 'retarget solution' process, so you can revert to the previous state for troubleshooting etc.
An example:
I'm want to build an old version of librdkafka, which was originally built with VS2010, and I want to use VS2017.
when looking at the solution explorer pane, you can see all projects has "(Visual Studio 2010)" title near them, at the left side of each project name.
Now I right click on the solution, and select 'Retarget solution':
At the dialog box, you get, click OK, and that's it.
Do we have some alternative plugin for python behave for jumping from feature file to step definition.I know Behave BDD Support is available in professional edition.
So do we have something to achieve jumping feature in pycharm community edition or any other tool.
Unfortunately, there is no alternative to PyCharm Professional edition. I tried XCode with different plugins, but they provide only syntax highlighting. Community edition also provide syntax highlighting without jumping feature.
There is Visual Studio Code for Win, Linux, and Mac, and nice extension, which allows to have code-navigation from feature file by CTRL+Clicking a step to its step definition. The extension is Cucumber (Gherkin) Full Support. I have just pushed a small behave project for checking the extension settings.
Install Visual Studio Code
Install the extension for Visual Studio Code
Clone the project and check the navigation from features/one.feature file to features/steps/definitions.py
use the .vscode/settings.json for your project
The extension also allows to have snippets as you type.
I'm moving my old project to Visual Studio 2017 [from 2015], but whenever I try to edit a RDLC report in VS it updates my report version and makes it incompatible with 'Microsoft.ReportViewer.WinForms' version 10.0 using 12.0.
The thing here is that I need to keep the version, because every user has the v10.0 DLL aside the project so I could not update everyone at once.
I tried to embedded that DLL into the executable but it says this:
Cannot embed interop types from assembly
'Microsoft.ReportViewer.WinForms, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91' because it is missing the 'Guid'
attribute
Any help or workaround would be appreciated, thanks in advice.
For anyone wondering how to do this, I didn't found a workaround.
Instead I decided to upgrade to latest ReportViewer version [10.0 -> 14.0] as it has retrocompatibility, it can read older reports and I don't have to upgrade them.
In other hand for the fact that I have several user installations with the DLL in the same folder of the executable, I have an automatic tool which allows me to update any assembly without much effort. This tool is made by me, so I can't tell how to do it other way.
I have developed a .bpl package with some components. I did this in C++ Builder XE7 and to install it I could just select "Install package" (or something similar) by right clicking on the .bpl project (in the project manager).
Now I have updated to C++ Builder Tokyo (10.2) and there is no alternative to install/uninstall the package from the project manager.
Has this function been moved/renamed? Do I really have to do it manually?
EDIT:
I solved it. For anyone having the same problem, It seems like the import from XE7 into 10.2 doesn't work that well. I opened it in 10.1 and there the install option became available. Then I opened that project in 10.2 and everything went fine now...
Make sure Win32 platform is selected when you want to install. Since IDE is a Win32 app, you can only install win32 components in it. The other platform targets just use components blindly. This causes other issues that Embarcadero has put on back-burner for way too long for example they have not done anything about RSP-10456 since I reported it when XE8 was in beta.
We are using Visual Studio 2008 to develop a winforms application stored in Visual Source Safe 2005.
If one of our team members changes a *.Designer.cs file without changing the form's source file the change doesn't appear during a "Get" operation. However, if in Visual Studio you run a compare on the *.Designer.cs file the differences are displayed in the difference viewer.
FYI: We are using the default Microsoft Visual SourceSafe plug in for Visual Studio.
Any ideas why the "Get" operation will not detect changes in the *.Designer.cs files and suggest we pull down the latest version?
Thanks for your help!
Designer files are not intended for manual manipulation. One of the chief incentives for adding partial classes to the popular .Net languages was to segregate the designer-generated code from manual user code, in fact. Manual manipulation of repeatedly-generated code (in pretty much any environment, not just visual studio) is asking for headaches.
What changes are you making to the designer file, and why is it not possible to make those changes to the non-designer source file?
Edit:
Is the project in the IDE properly bound and connected to the source control database (via File->Source Control->Change Source Control)? It should automatically be checking out the designer files when changes are made in the designer view.
I would try doing a Get manually through VSS Explorer (i.e. not through Visual Studio) and see if it works. If not, check to see if the file is pinned to a previous version.
Woe unto you for having to use SourceSafe. At my last job, we used SourceSafe and had a myriad of problems with it. We switched over to Surround SCM and were really happy with it. I'd never heard of it before that job.
To answer your question, any time I ran into a problem like this with SS, I'd do a "forced get": in the options dialog when you get latest, tell SourceSafe to get the latest version from the server regardless of whether it thinks the file is up to date.
Edit: I think the issue is the VS200X plugin for VSS. If you have the VSS standalone application you should be able to do a forced get from there. I now remember having to do this so often that I stopped using the VS200X plugin.