479
I was able to get my .app file signed, but I am noticing that when I make a change to my AL extension, the .app file gets replaced by a new .app file without the digital signature.
I am wondering if resigning the .app every time is the standard or if there is another method of keep the .app file signed?
If you use f.ex. Azure Devops or Github you can build build / release pipelines that automates the process for you.
You can find alot about this CI/CD approach f.ex. on freddys blog.
There are also some add-ons avalible for Azure Devops that can help you automate your build process.
You will find info about that solution on f.ex waldos blog.
Hope this helps you further.
You have to sign the app. file every time you produce a new build.
The signing is there to prove that the file have not been changed after it was signed
AppSource will also require you to change the version no. for every change you make.
So every time you change something and build the app file you will have to sign it again.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
288,584
Super User
#2
Martin Dráb
225,864
Super User
#3
nmaenpaa
101,148
Share
Report
All responses (
Answers (