Open innonav-dev opened 10 months ago
@AdminHodor @waldo1001 Any updates on this matter?
Kind regards.
We have absolutely no clue why it doesn't work anymore. Is there documentation to how to compile the baseapp? What the settings are?
The changed probing path was necessary - I just don't remember why. It was yet another undocumented change in how they build artifacts 🙄.
Changes in probing paths was necessary because of difference in versions when they included the "code .net" stuff .. .
As we are not able to repro, we did some changes. When published, I'll ask you to test again.
We can't reproduce, but we have investigated and have a clue why it might fail on your end.
Fixed in v1.466
Describe the bug When we try to build our custom MS Base App on BC 23.1, we get compile errors that dotnet assemblies are missing.
the used yaml
the output Without the AspNetCore directory:
With the AspNetCore directory:
Expected behavior The Base Application should be compilable without adding additional add-in directories.
Additional context When we don't add any additional probing paths, most of the assemblies are missing and we get a lot of errors.
When we only add the
"../Service/Add-ins"
directory to the probing paths, then the AspNetCore.StaticFiles add-in is missing.And when we add the AspNetCore directory to the probing paths, we get a lot of convertion errors regarding the OpenXML add-in. It seems that the different assembly paths contain different versions of the DocumentFormat.OpenXML assembly.
We also compared the new build to our old succeeding build with BC version 19 and saw that you changed one probing path from
"C:\program files\microsoft dynamics nav\230\service"
to"C:\program files\microsoft dynamics nav\230\service\management"
.What's the reason behind this and can you fix the probing paths for BC 23.1 so that the Base Application is compilable again?