Quentin Tresontani

@hemisphera - Coming back to this issue after a long time.... Is this still something that you are experiencing on newer Business Central versions? Is it still impacting you? A...

@Gwrsky - We tried to reproducing he issue that you mentioned on the latest preview of Business Central, and it works as expected. This is how the action bar looks...

Closing this issue as we couldn't reproduce it. If you are still experiencing it without having other extensions or in-client customizations on your environment, please log a new issue with...

Closing this issue because it has been inactive since November. If you are still experiencing this, please log a new issue with additional information

@RadoArvay - Can you share a simple project/workspace (including the baseline versions) that reproduces the issue?

@RadoArvay - Sorry for the delayed answer. Removing the version property in the AppSourceCop.json will disable the breaking change validation including AS0064. That can be a temporary workaround, but prevents...

Ok, I actually can get a repro by having this code in the dependent app, but only if I don't set tup my baseline packages correctly. My code for the...

The problem with using the `al.packageCachePath` for both the dependencies of your current version and the baseline package is that the baseline package's dependencies will be resolved to the latest...

Using 'al.compilerOptions.outFolder' will allow you to push the package built for your project toward a specific folder. It doesn't influence the resolution approach as such, but since the resolution relies...

Hello, without more information, it is hard to narrow down what is causing it. Are you experiencing this issue when debugging a local server or docker, or when using a...