Let's put an App on AppSource Part #4

Поделиться
HTML-код
  • Опубликовано: 12 ноя 2024

Комментарии • 10

  • @JosepPages7
    @JosepPages7 2 года назад

    The experience of publishing to AppSource can be a bit frustrating, but I'll give it a try. Thank you very much for all the videos about this serie, I'm sure they will be of great help to me.

  • @greatscott000
    @greatscott000 3 года назад +2

    Eric, would you do (or do you have) a video on handling translation files? Would love to know more about your translation tool in your build process.

    • @Hougaard
      @Hougaard  3 года назад +1

      Maybe some day :)

  • @rolandthompson6071
    @rolandthompson6071 3 года назад

    Great video series, very useful. Second the comment by Todd Scott - would also be interested in the handling of translation files, plus also the entire build process you do.

    • @Hougaard
      @Hougaard  3 года назад

      Will do at some point in time :)

  • @Efryed
    @Efryed 2 года назад

    Good video but I have a doubt, how can I do to put a price to the app, my purpose is to sell the app, but in the steps you followed I did not see something about that.

  • @4strings2play
    @4strings2play 3 года назад

    Hey Erik, first of all thank you for all your Videos =)
    Right now i have a topic im not quite shure about and i didn´t found the right documentation for this till now. maybe you could help with your knowledge =)
    If a Customer wants to use Business Central on Azure as SaaS, am i still be able to develop apps for that Customer and upload them directly? (without using the AppSource) and what requirements and restrictions did such an app have?

    • @Hougaard
      @Hougaard  3 года назад +1

      Yes, you can upload extensions as PTE to a production environment.

    • @4strings2play
      @4strings2play 3 года назад

      @@Hougaard must every Rule from the PerTenantExtensionCop be met? Or is it possible to install even if not all Rules are met?
      (some Rules are displayed as Warnings, Some as Errors)
      we´re developing in our own ID range but the PTECop said it MUST be in range [50000..99999]
      VSCode displays it (PTE0001) as a warning but the MS doc for "PerTenantExtensionCop Analyzer Rules" says it should be an Error..

    • @Hougaard
      @Hougaard  3 года назад

      @@4strings2play You can only deploy your own ID range to a cloud tenant through AppSource, not as PTEs.