I saw this question about associating files without extension as .xml and it made me curious how to achieve this for .wsb Windows Sandbox configuration scripts.
How do I make all .wsb files open up as .xml files by default in VS Code?
Related
We're trying to maintain a single set of Visual Studio Code extensions within our organisation, managed centrally. In our ideal scenario all end users have the same extensions installed, those extensions are updated on their behalf, and they are not able to install additional extensions.
We had achieved this to date by:
Installing extensions to a directory under C:\Program Files and setting the (undocumented) VSCODE_EXTENSIONS environment variable to point to that location.
Configuring a scheduled task (run as SYSTEM) that executes a powershell script with a list of extension_ids that calls code install-extension <extension_id> on each.
This solution worked until a breaking change in v1.74 expected to be able to write a new extensions.json file to the extensions directory.
Whilst we can get around this by creating a extensions.json file in that directory, I don't want to go too far down the wrong path. Is there a preferred method for centrally managing extensions for Visual Studio Code?
I have been using Atom for a long time, at the end it has been just for comfort but for the last few weeks I have been using VS Code, and I am delighted with the IDE, so I want to completely migrate to it.
But the only thing I'm missing from VS Code is the functionality that Atom Editor has with the ftp (ftp-edit extension) plugin that allows me to navigate through the ftp directory without previously downloading the files, just when I open files or directories in IDE perse. Instead the extension ftp-simple of VS Code doesn't allow me to use this functionality (or at least I haven't know how to find it) so I have to download the entire ftp tree, and on each connection I have to wait as long as it takes to get off.
Any idea about this configuration or if this is any parameter in some config file?
I know about the other stacks but I didn't recive any answer for this.
Cheers!
Here is a simple description of my problem. If you need more information please inquire.
I am not seeing any way that you would be able to sync files from my local computer to another file server. Is there a way that this would be possible using Visual Studio Code and a mapped network drive file server?
https://marketplace.visualstudio.com/search?term=sync&target=VSCode&category=All%20categories&sortBy=Relevance
You can sync files to another machine via a plugin called 'ftp-sync' this will allow you to send files to a destination via the FTP or SFTP protocol. This plugin also allows automatic upload on save (which is awesome).
See Url: https://marketplace.visualstudio.com/items?itemName=lukasz-wronski.ftp-sync
I have a Project Group in Visual Studio 6 (.vbg). The projects are under source control (TFS). When I start debugging Visual studio there is an error Path/file access error: Path/name.vbg and dialog for "Save Project Group As" follows when canceled debugging runs without problems. To circumvent this annoyance I need to have the group file checked out or mark as readable just by file attribute. Is there a way how to avoid this behavior?
Notes: Situation was the same when Visual Source Safe was used. By my observation .vbg is not changed when the change is allowed. The problem can be connected with using English Windows with non English regional settings.
No. Just keep the VBG in version control, and make the files read-write in your local directory.
The easiest solution would be for you to save your VBG files to a folder outside of source control. It won't make a difference to the running directory - that is based on the EXE project (if any).
On my mac I mounted a shared drive using WebDAV by going to "Finder > Go > Connect to server".
Now, when I try to view the files using TextWranger or TextEdit I can see the PHP code that I want to edit.
However, if I try to use an IDE like NetBeans/Eclipse/TextMate and create a new project with my shared drive as the "Existing sources" folder I cannot see the PHP code.
Instead I see the HTML output of the files as if I were seeing them through a web browser. Also, if I try to view a file that isn't normally accessibility (a command line script) I see the output as if it were called from the command line.
But a weird thing is if I use TextMate to edit a single file from the shared drive I can see the php code I am trying to edit. It just doesn't work as a project.
Any suggestions or solutions on how I can use an IDE to edit files over WebDAV? And why do my IDEs display the content rendered, instead of the actual file on the file system.
I'm not a specialist at all but I seem to remember that WebDAV clients do send GET requests.
If I'm correct your server may not be able to discriminate between HTTP GET and WebDAV GET thus rendering your .php files. Why this would work that way when working with a project and another way while working with individual files is not clear, though.
Do you get rendered files when you add files to your project manually as well?