You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to add a function to identify which packagetype an AppFile is?
Example:
I have a file MyApp.app, but I dont know if it can be submitted to AppSource. AppSource packages cannot be RuntimePackages.
I propose a function to identify what type of apppackage it is.
I believe this can be done via reading the first 50 bytes of any given app file and identifying patterns in the file.
The usage for this function is for New-AppSourceSubmission, which requires a regular AL-package.
Another solution to the problem would be to add the functionality to altool.exe, such that the information would be present when calling Get-AppJsonFromAppFile.
If this is accepted, I will provide a pull-request with the functionality.
The text was updated successfully, but these errors were encountered:
Just to be pedantic an appsource submission file also contains source code and must be digitally signed.
eg: The first four bytes of this sort of file say NAVX, it must be a valid ZIP file (the PK\3\4 at offset 40), the zip file must contain source (At least six files in the zip?) and there must be a digital signature (Hmm, NXSB at end ?).
Would it be possible to add a function to identify which packagetype an AppFile is?
Example:
I have a file
MyApp.app
, but I dont know if it can be submitted to AppSource. AppSource packages cannot be RuntimePackages.I propose a function to identify what type of apppackage it is.
I believe this can be done via reading the first 50 bytes of any given app file and identifying patterns in the file.
The usage for this function is for
New-AppSourceSubmission
, which requires a regular AL-package.Another solution to the problem would be to add the functionality to
altool.exe
, such that the information would be present when callingGet-AppJsonFromAppFile
.If this is accepted, I will provide a pull-request with the functionality.
The text was updated successfully, but these errors were encountered: