I, in fact, do have the other use case where I want to export all contents of my project to my filesystem so that I am able to use local, client-side Git as VSC. But I always get the same error message "There are no folders in the current workspace ..." like reported by @Pietro Di Leo 

But my workspace has folders, so I don't understand what's missing to use this feature or if it is a bug.

@Brett Saviano do you have any suggestions for the use case?

I even took a look at the vs code extension sourcecode, but did not understand which exact conditions lead to the error message: https://github.com/intersystems-community/vscode-objectscript/blob/14bd8...
 

I solved this as described in the following post (and comments): https://community.intersystems.com/node/507036

But since this approach is somewhat cumbersome and some time has passed since, I wonder if anyone has found a better way to deliver static files via WebApp and put the IRIS login page in front of it for authentication?

Since having AutoCompile enabled comes with security issues and won't even work out-of-the-box from IRIS version 2025.1 onwards (see https://docs.intersystems.com/iris20251/csp/docbook/changes/index.html#C...) I came up with a solution without the need of enabling the AutoCompile-option in the WebApp:

We just have to make sure that the index.csp is compiled once. To do so, we call $SYSTEM.CSP.LoadPageDir("/my-app", "ck") right after we create the WebApplication programmatically.

Example from our IPM module.xml:

    <!-- Compile all csp files of webapp /my-app -->
    <Invoke Class="%SYSTEM.CSP" Method="LoadPageDir" CheckStatus="true">
        <Arg>/my-app</Arg>
        <Arg>ck</Arg>
    </Invoke>