Skip to content

Documentation for migrating from classic mode to manifest mode #425

@g40

Description

@g40

Type of issue

Documentation/Best practice

Description

are some clues as to how to transition to manifest mode. For example, the manifest needs to have a GIT commit ID, which can be hard to find. Especially for multiple packages.

Various sources recommend vcpkg x-update-baseline --add-initial-baseline but the experimental option is a concern.

What are the recommended actions?
Will this scenario be handled by some yet to be seen tooling for VS?

Thanks for listening.

This might also mitigate microsoft/vcpkg#41171 (comment)

Page URL

https://learn.microsoft.com/en-us/vcpkg/consume/manifest-mode?tabs=msbuild%2Cbuild-visual-studio

Content source URL

https://github.com/Microsoft/vcpkg-docs/blob/main/vcpkg/consume/manifest-mode.md

Document Version Independent Id

09fd1386-6491-3c4e-8704-e25c041d540a

Article author

@vicroms

Metadata

  • ID: 09fd1386-6491-3c4e-8704-e25c041d540a
  • Service: vcpkg

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions