Scenario result in VS Code shows both table view as well as transaction view at once (Windows 10 - clean install)

Questions
1

Mod note: As of SDK 1.5.0 Scenarios have been superseded by the more powerful Daml Script. We now recommend using that for all purposes. For more information, and to learn how to use Script please check out @Andreas’ post on our blog.

I have installed the prerequisites and vscode on a clean new windows installation.

When creating a new DAML project with daml new ... and looking at the scenario result in VS Code, I was presented with both the transaction view and the tableview at once. The button responsible for switching views also showed both options.

See here:

image
image847×1271 64.5 KB

Any ideas how to fix this?

2 Likes
2

I don’t think I’ve ever seen this. Could you provide some details on the SDK, the version of Windows and the version of vscode you are using? I just tested this using SDK 1.0 on Windows 10 with VSCode 1.44.2 and I am (sadly?) unable to reproduce this. If you have the same versions, then my guess is that somehow the VSCode extension is not installed properly. In that case, I would try the following steps:

  1. Close vscode completely.
  2. Run code --list-extensions --show-versions. Since you said this is a fresh installation this should only show DigitalAssetHoldingsLLC.daml@1.0.0. In particular, there should be no DigitalAssetHoldingsLLC.daml-bundled.
  3. Run code --uninstall-extension DigitalAssetHoldingsLLC.daml.
  4. Run code . in your project. At this point you should get no syntax highlighting or anything else. Leave it open for at least 10 seconds (vscode has an extension cache that will be reset after a short delay).
  5. Close VSCode completely and run daml studio again.
3 Likes
3

Your steps above fixed it. It was apparently a broken VS Code plugin installation (not that I have a clue how this could go wrong though).

I’m assuming that the windows and VS Code versions are not relevant anymore, as no one will probably be able to reproduce the issue.

1 Like
4

Glad to hear that you got it working! Sadly, I don’t have any idea either how the installation could go wrong :confused:

1 Like