|
I asked one of the programmers on the Code integration and he thinks my guess is probably right, that your 1. and 2. are the same issue. It's discussed in the pending user manual topic for VS Code that hasn't yet been published. From that topic: The system searches `%USERPROFILE%\.vscode\extensions\` looking for `manifold.manifold-sql-*`. However, the CLI installs wherever VS Code actually looks, which is the same place for a stock installation but a different place for Insiders (`.vscode-insiders`), for a portable layout, or for a configured `--extensions-dir`. It might be something else, but I think the above is worth looking into before chasing more exotic possibilities. If that's the issue (and if not, I don't like it that custom/portable/insiders installs have an issue) I think Manifold should expand the logic so users don't have to worry about. You can help nail this with some data: What's your VS Code version, and is it stable or Insiders? Also whether both are installed. How VS Code was installed? user setup, system setup, portable, or a package manager? Is --extensions-dir configured, or has code.cmd been wrapped or aliased? What is the output of Code --list-extensions --show-versions filtered for manifold.? What is the directory listing of %USERPROFILE%\.vscode\extensions\ filtered for manifold? When you do two consecutive query launches in Manifold, what are the log lines around those? Does an "installed the Manifold SQL extension" line appear on both? If so, that's a direct confirmation of the loop. If not, then it's likely something else. You published an extension for Manifold SQL. Is that installed alongside? If you like you can send answers here or send them together with a report to tech support. I just wanted to push the info from the pending topic to here in the forum in case anybody has a non-stock VS Code installation.
|