I have a couple of projects with bdsproj files and I know they were created with Borland Delphi 2005. Is there a way to open these projects in Visual Studio Code? What settings must be present?
There is no support for .bdsproj files in OmniPascal.
You can load the corresponding .dpr files of the projects in order to get code completion etc but there is no support for automatic generation of build tasks.
Related
I'm currently working for a new company, where most of the guys develop in Visual Studio 2017 (vs2017). I really like it, but feel more comfortable working with Visual Studio Code (vscode), and because, my work does not require any build processes.
Here's the workflow: I've put the workspace folder in C:/ directory, and open it through vscode. Whenever I apply code changes, the results are visible in vs2017 IDE. But when I create new folders/files in vscode, I don't see it in vs2017...
And because files/folders are not synched, I feel stuck using vs2017. An alternative is to do these operations on vs2017, and code in vscode. But I don't see this as a beneficial and efficient in hindsight.
To summerize, how can I create files/folders in vscode, or lets say in sublime/atom/brackets for that matter, and see it in vs2017?
Solution to my question can be found here.
In short, you have to enable show all files in solution explorer in vs2017, then right click on the newly added folder (marked in gray), and click include in project.
I recommend doing this everytime you open vs2017.
PS! Open for other alternatives where you can skip this process, it may be stress to do this when project scales.
I'm porting two AS3 projects to TS using Visual Studio Code.
The second project uses code from the first project's folders.
I wonder if it is possible to specify additional source folders outside the main source folder in Visual Studio Code, like in the old good FlashBuilder.
For example:
Main source folder: "src"
Additional folders: ["../previous_project/src", "../previous_project/libs"]
This way I can use or extend classes from the external projects like if they were saved in the main source folder.
Investigating a bit I've found that the 'Insiders' version of Visual Studio Code have something called 'multi-root workspaces'. I made some experiment with it, but I must be doing something wrong: When compiling, I get:
"error TS6059: File is not under 'rootDir'.
'rootDir' is expected to contain all source files."
So, how do I specify additional source folders in Visual Studio Code?
After playing a bit more with workspaces, it seems that commeting out "rootDir" in tsconfig.json removes 'error TS6059'. Now I can compile with no issues.
It would be good to see a correct example of multi-root workspaces, though.
We've updated to Visual Studio 2017 and switched to Team Services (VSTS) as our source control. I've migrated a few old projects and am using the Microsoft Installer Project extension to provide compatibility for the original setup projects.
However, there seems to be a potential issue with source control when working with the setup projects. Attempting to make any change results in the error:
The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out.
Modifying files of other projects within the solution work correctly and trigger checkout from the repository.
I have not been able to determine a way to properly check out the setup project and work with it under the new source control. I'm unsure if it's a bug with the extension or if it simply lacks support for VSTS.
Has anyone successfully been able to work with setup projects (.vdproj) in conjunction with VSTS? If not, is there a workaround?
Edit:
Image of context menu:
You can apply the following workaround, since it seems to be a bug in the installer extension:
Choose 'Open file in File explorer' in your context menu
Open the project file in your favorite texteditor
Make a dummy change (adding a space character in an empty spot is enough)
Visual studio will prompt to reload the project and has explicity checked out the project file.
see also here
I submit a feedback here: The command you are attempting cannot be completed because the file 'Setup[Productname].vdproj' is under source code control and is not checked out
The workaround is that you can check out the project manually. (Right click the installer project > Check out for edit)
Is there a option to create new files like in Eclipse? When I create a new file in Eclipse, there is a dialog with classname, main method, etc.
I want to do this in Visual Studio Code too. I don't really want to write a class from nothing by myself :D.
This is currently not supported. Visual Studio Code is more lightweight than Eclipse and Visual Studio.
I would like to create custom Path Macros in Visual Studio. I know there is another topic on this but that one only works for Visual C++ projects. I'm not writting a C++ project so the Property Manager isn't available.