Skip to content

Create tooling to update files in packaging.psm1, files.wxs, pwrshcommon.cpp automatically #6978

Closed

Description

@SteveL-MSFT

Whenever we reference new packages or existing packages add new assemblies, we go through a manual exercise to update source files. This should be automated and manually reviewed.

Activity

  1. TravisEz13 commented on Jun 5, 2018

    @TravisEz13
    Member

    Whenever files.wxs is regenerated, The following properties about existing components cannot change or patching will be completely broken:

    • Component Id
    • Component GUID
    • File Id
    • File Name (the source path of the file, however, can change. Although, the destination cannot change, but that is in a separate WXS file)

    This assumes we stick to the WiX recommendation of one file per component. If we don't, the rules become more complex.

  2. iSazonov commented on Jun 5, 2018

    @iSazonov
    Collaborator

    If the script find and report what lines we should remove or add why we can not edit the file automatically? It is not regeneration of the file from scratch.

  3. TravisEz13 commented on Jun 5, 2018

    @TravisEz13
    Member

    Ilya (@iSazonov) basically, its just more work and it hasn't been done. I'm just listing the requirements for the work, which may not be obvious. We cannot just use the WiX toolset to generate the file and replace the existing file.

  4. iSazonov commented on Jul 30, 2018

    @iSazonov
    Collaborator

    Travis Plunk (@TravisEz13) has already updated packaging.psm1 in #7272.

  5. microsoft-github-policy-service commented on Nov 16, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

  6. microsoft-github-policy-service commented on Nov 23, 2023

    @microsoft-github-policy-service
    Contributor

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions