What external tools do you use for Ignition development, and why?

Ignition
61

They should be relative to the position of the saved VS Code workspace.

So if you do "Save Workspace As" in VS Code, wherever you choose to put that file (We typically do it in the root) of the repo, then it would be relative to that.

image
image381×278 46.5 KB

Typically we are using this extension with gateways running in docker containers, and not on direct windows installs, so arguably I have not ran through that specific scenario before.

You could try creating a VS Code Workspace in your C:\Program Files\Inductive Automation\Ignition\data directory, and then setting the paths to just be projects?

Or you could try making the workspace in your home directory for your user, and then putting in a full hardcoded projectPath for C:\Program Files\Inductive Automation\Ignition\data\projects? Here is a proposed workspace file for that setup. If you make a folder (wherever you typically use as a working directory, lets pretends its C:\Users\username\ignition

With the file at C:\Users\username\ignition\ignition.code-workspace.json

{
	"folders": [
    {
      "name": "Root", # Reference to C:\Users\username\ignition
      "path": "."
    },
    {
      "name": "Projects Directory",
      "path": "C:\Program Files\Inductive Automation\Ignition\data\projects"
    }
  ],
	"settings": {
    "ignitionFlint.ignitionGateways": [
      {
        "label": "Ignition",
        "address": "http://localhost:8088",
        "projectPaths": [
          "C:\Program Files\Inductive Automation\Ignition\data\projects"
        ],
        "updateDesignerOnSave": true,
        "forceUpdateDesigner": true,
        "supportsProjectScanEndpoint": true
      }
    ]
	}
}

Caveat, that I dont have access to a windows computer at the moment and so I did not test that at all.

2 Likes