did anyone else try to use the VS Code Extension on Linux? VS Code works on Linux, so I thought the extension would, too. Turns out I can connect to a CF server and use the RDS stuff, but, I cannot create a project. Upon reporting this, I was told the extension works supports Win and Mac only. But, given that MacOS at it's core basically is a BSD variant, I can't be too difficult to modify it so that Linux users can use it as well, can it?

It is possible we may work towards that end. However, Linux users (development, not server) are a miniscule percentage of our developer base. Also, and you know this, it isn't "Linux". It is a wide range of flavors of Linux that are available, with different packages that may or may not affect how VS Code interacts with the UI, with the file systems, etc. Not saying it won't happen, but it will probably take a while. I'm actually curious though how well it would run under something like Proton.

@Mark Takata (Adobe) seeing that many things already work on "Linux" 😜 I really can't imagine that creating a project in the file system would be that hard to get working. Even the folders and files for the CFML project are created, they are "just" not shown in the pod (I realize that it may be more than just displaying them!). Plus, server connection, RDS datasource stuff, RDS file system stuff, autocomplete, intellisense, that all working. Actually it works well enough to use it in my daily work. And of course I do realize that I may be among a small minority, but, hey, compared to the amount of work it took to create this extension, it should be just a miniscule percentage of the total work load. 😉

Does the lack of Linux support also pertain to people like myself who use a Windows PC but run VS Code in WSL? That would explain a number of the issues I've been seeing.

I run VS Code on Windows but use WSL2 for all my "server-side" development so I rely on the Remote-WSL2 extension to support that. I haven't tried the new extension yet because I haven't needed to work on CFML code since it was released -- but seeing this thread and also the complaints about it messing with people's theme settings etc makes me very cautious about it, at this point.

Feel free to add a Feature Request into VS Code Extension in Tracker for adding Linux support, including WSL. If there's enough requests for that I'm sure we will look into adding that.

When I next need to do some CFML work, I'll try the extension out and report back on how well it does/doesn't work with VS Code on Windows and all the files on Ubuntu via WSL2 🙂

Sigh. Cross platform editor with a non-cross platform extension. Install extension (PopOS 22.04). Restart VSCode. My laptop fans almost instantly come on LOL and I can tell this isn't for me. 😕

Ha. This is interesting. I couldn't get it working in Windows 10, so I booted up Zorin OS 16.1. Another Ubuntu flavored desktop. It actually worked, in terms of loading the dialog windows and letting me enter server settings. I didn't get too much further as I'd have to connect it to the proper network, etc. Now back to trying to figure out Windows 10..

I can confirm that it mostly works on Zorin OS 16.1, but debugging appears broken because it tries to open files using a path that is all lowercase regardless of what was configured and is actually the case, such as /dev/someproject/index.cfm instead of /dev/SomeProject/index.cfm. FYI, all my testing was done running a local server using CommandBox.

doesn't seem to work when using with remote wsl. which is a shame.