Closed Arthurvdv closed 3 months ago
Same here! :)
Same here!
Something simular here
We have been able to repro it.
No need to mention: Microsoft is breaking stuff, and not documenting what they are breaking, so we need to reverse engineer what causes this. MOst probably the altool, but why they broke the dll - weird. This takes time - and it wouldn't be the first time that it's just "work in progress" and one of the next vNext-versions, it would suddenly start to work again .. .
You're not going to believe it.
Dlls used to be here: program files/Microsoft Dynamics NAV/240/Service Then, they moved "a few" dlls to program files/Microsoft Dynamics NAV/240/Service/Management
Now .. they renamed SOME dlls (replaced "Dynamics.Nav" to "BusinessCentral"), forgot about the namespace, and moved the compiled dlls to: program files/Microsoft Dynamics NAV/240/Service/Admin
All 3 places still exist - and we used to have versioning-issues in the past.
😱
We'll fix it - but I expect it to not work in the very near future 🙄.
We'll fix it - but I expect it to not work in the very near future 🙄.
Is my assumption right we're using these App Management dlls for retrieving the details from a (runtime) app file? I'm asking this because with the new altool (https://github.com/HodorNV/ALOps/issues/719) I believe it's possible to remove the depedency to these App Management dlls, which are indeed subject to change at the most inconvenient moments.
altool only gives details of the manifest and is able to create symbol file. We need more (on some tasks).
We are looking into the altool, but we definitely needs the rest of the cmdlets as well ..
Hi @waldo1001, any update on this. Is there for the time being a workaround for this, or do we need to wait for a fix?
Hi @waldo1001, any update on this. Is there for the time being a workaround for this, or do we need to wait for a fix?
We are struggling with this one. Any timeline on this?
We're working on it.
All of a sudden, Microsoft moved their libraries, and only made it possible to run them in PS7.
DevOps doesn't "just" allow to create tasks that run in PS7.
So we have to find workarounds (there are - but it takes time to implement them in 21 steps... :( ).
We have it working for the compile-step, but since this is a MAJOR redesign and major refactor, we need to thoroughly test it.. and then apply it to all other steps.
Should be fixed in latest release (v1.463) - please test thoroughly (we had to do quite some surgery to make it work)
Thank you for making this huge refactor in a relatively short period of time.
It looks promising and as a bonus we see a performance gain in the duration on the ALOpsAppCompiler@2 up to a whopping 200% 😲
Thank you @waldo1001. The problem seems to be fixed.
Describe the bug The ALOpsAppCompiler@2 is failing on the Next Major artifact.
##[error]Cannot bind argument to parameter 'Name' because it is null.