You’re offline. This is a read only version of the page.
5
Hello,
why do I need to sign my code when I want to publish my App on a On-Premise Version via PowerShell ?
The extension is just effective for my business partner and nobody can download it, so why do I need to sign my code then ?
My next question would be, why am I allowed to upload my code unveryfied and how will this affect the application ?
I need some clarification please :)
Thank you in advance !
It is still good practice to code sign all apps, but yes, you do not need to do that for in tenant apps. The reason why it might make sense to code sign it is that you can be sure that it is valid and was not "customized" in any way after you released it. For instance, you create a version of the app that you are deploying to one tenant only. You code sign the app. You then make a change to it, but don't want this to be used, because it's a work in progress.
By accident, you use the wrong version and deploy that one. You will get an error that the app is not code signed and therefore know that you tried to deploy the wrong version.
In general, it is not required to do this, but code signing certificates are not really expensive and just that little extra peace of mind to it - and also makes it more "professional".
However, there is one other thing: If you are deploying an app on premise, you need to use the developer license, because otherwise you cannot deploy the app, if you have some "special object range" (not 50,000 range). The way around this is to create a runtime package. And these runtime packages cannot be code-signed as of now, at least I have not found a way, since I am getting errors that it's not a valid file when trying to code sign it.
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...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (