icon

Foro de Soporte Allplan

[Pregunta] Create Visual Studio Code Workspace

JanRei
JanRei
06.06.2025 - 09:37 *

Hi,
I am trying to set up a workspace with Visual Studio Code. To do this, I run the script “Create Visual Studio Code Workspace”. After I have selected a file path and clicked on save, nothing happens. No .code-workspace file is created.
Does anyone have any idea what the problem is?

Thank you.
Greetings
Jan

Brücken und Ingenieurbau
VIC Planen und Beraten GmbH
https://www.vic-gmbh.de/

Adjuntos (1)

img
Save.png
Type: image/png
Descargado 33 veces
Size: 55,03 KiB
bmarciniec
bmarciniec
10.06.2025 - 08:57

Hi Jan,

can you give us more hints? There is no pop-up message saying "An error occurred, please see stack trace for more info."? Do you have the trace window open (you can activate it with CTRL+F3)? Try to save the workspace and see what gets printed. The message would help us to figure out, what is wrong.

Cheers,
Bart

jvelletti
jvelletti
11.06.2025 - 09:45

i am just "guessing":
pylint not installed?
then the checkbox "use pylint" should not be active

Allplan Webentwicklung

Private messages must be private. No support request via Private message.

JanRei
JanRei
16.06.2025 - 10:51

There is no error message in Allplan. Here is the content of the trace window.
I have tried both: “use pylint” active and not active. No difference

Brücken und Ingenieurbau
VIC Planen und Beraten GmbH
https://www.vic-gmbh.de/

Adjuntos (1)

Ausgabe.txt
Type: text/plain
Descargado 3 veces
Size: 1,29 KiB
bmarciniec
bmarciniec
17.06.2025 - 12:02

I cannot see any output coming from the python interpreter here. Maybe let's do it this way:

  • Go to AllMenu -> Service -> Allplan logging (trace) -> write to "Allplan.out" file
  • Close Allmenu to make sure, the setting is saved.
  • Start ALLPLAN
  • Try to create the workspace
  • Close Allplan
  • Open Allmenu again and go to Service -> File explorer -> My own temporary data
  • There should be a file allplan_python.out. Please share the file with us.

I assume, you are using ALLPLAN 2025-1 or newer. BTW, there is an issue with the trace that python is not printed there directly after you turn it on. You have to restart ALLPLAN. This is probably the reason why I can't see anything python related in your log snippet.

Cheers,
Bart