Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-24455

Windows: Allow custom Extensions in manifest root

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects Version/s: Release 6.0.0
    • Fix Version/s: Release 6.1.0
    • Component/s: Windows
    • Labels:
      None
    • Story Points:
      8
    • Sprint:
      2017 Sprint 06 SDK

      Description

      Following up from TIMOB-24282

      In tiapp.xml, we should be able to define Extensions in App's root, not under the Package's root.

      " it is mentioned that by modifying tiapp.xml, one can add Extensions and while it was tried, it seems those elements are copied inside the App's root and not the Package's. It needs to be in the latter.

      With that being said, there is also a mention of using CMake to include files and it seems that this approach regenerates the solution file. That being so, if there is a way to use that approach such that the we can add compile-time references to some of the third-party binaries (that is, not just include them as "resources"), I believe Visual Studio will also add the appropriate elements to register the classes from the SDK in the Package's AppManifest.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kiguchi Kota Iguchi (Inactive)
                Reporter:
                kiguchi Kota Iguchi (Inactive)
                Reviewer:
                Gary Mathews
                Tester:
                Samir Mohammed
              • Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                    Git Integration