Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

outFolder does not allow publishing/debugging when configured #7676

Open
aipungggi opened this issue Mar 1, 2024 · 6 comments
Open

outFolder does not allow publishing/debugging when configured #7676

aipungggi opened this issue Mar 1, 2024 · 6 comments

Comments

@aipungggi
Copy link

aipungggi commented Mar 1, 2024

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:

  • AL Language: 12 and 13 (prerelease)
  • Visual Studio Code: 1.86.2
  • Business Central: 23.4

Internal work item: AB#548299

@aipungggi aipungggi changed the title outFolder stop working outFolder stopd working Mar 1, 2024
@aipungggi aipungggi changed the title outFolder stopd working outFolder stops working Mar 1, 2024
@aipungggi
Copy link
Author

aipungggi commented Mar 1, 2024

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
Copy link

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

@thloke
Copy link
Contributor

thloke commented Mar 26, 2024

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.

@thloke thloke closed this as completed Mar 26, 2024
@aipungggi
Copy link
Author

aipungggi commented Apr 15, 2024

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

@aipungggi aipungggi changed the title outFolder stops working outFolder does not allow debugging when configured Apr 15, 2024
@aipungggi aipungggi changed the title outFolder does not allow debugging when configured outFolder does not allow publishing/debugging when configured Apr 15, 2024
@thloke thloke reopened this Apr 16, 2024
@thellMa
Copy link

thellMa commented May 21, 2024

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
Copy link
Author

yes I have a similar projectstructure within a workspace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants