search

microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
722 stars 242 forks source link

outFolder does not allow publishing/debugging when configured #7676

Open aipungggi opened 4 months ago

aipungggi commented 4 months ago

Please include the following with each issue:

1. Describe the bug The following setting stops working from time to time and the app file is put in root again:

 "al.compilationOptions": {
        "outFolder": "\\\\aif\\Release\\Inbetriebnahme\\App"
    }

2. To Reproduce Steps to reproduce the behavior:

Cant reproduce it happens suddenly.

5. Versions:

aipungggi commented 4 months ago

I am using latest Prerelease (14) and at the moment the behaviour is: If I only publish, the app is saved to the path specified in 'outFolder'. When I start a debug session it says: [2024-03-01 14:02:06.66] Error: File c:\Users\ap.root\Amagno\src\Amann Informatik AG_***_23.1.0.15.app does not exist.

Few days ago this still worked fine.

Commenting out the outFolder setting and debug session starts but .app is put in root.

RadoArvay commented 3 months ago

Just connecting to #7536 - it was closed as solved but it has never worked correctly. Every type of setup has different result - always.

thloke commented 3 months ago

We've fixed a bug related to this recently, so I think this will be addressed in the next pre-release. It should be in version 14.0.965742 or later.

aipungggi commented 3 months ago

No this is not fixed. I am still getting "Error: File .....app does not exist." When outFolder is configured. v14.0.986719 (pre-release)

thellMa commented 1 month ago

Hi, I do get similar issue but with another relative path. I use workspace with multiple projects in them and want to place all app files in ..\builds\ folder, together with the .alpackage folder.

the folder structure looks like this.

App1
App2
builds
  .alpackage
  App1.app
  App2.app

Workspace file:

 {
    "folders": [
       {
           "path": "App1"
       },
       {
           "path": "App2"
       },
       {
           "path": "builds"
       }
    ],
    "settings" : {
       "al.packageChachePath": [
          "..\\builds\\.alpackages"
       ],
       "al.compilationOptions": {
          "outFolder": "..\\builds\\"
        }
    }
}

Everything compiles and I can download the symbols to this relative build path, but I cant publish the apps :-( all I get is

Error: File ..\builds\App1.app does not exists.

aipungggi commented 1 month ago

yes I have a similar projectstructure within a workspace