microsoft / microsoft/msix-packaging

MSIX Core solution uses deprecated std::experimental::filesystem

Open
#335 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-MSIX Core Feature
Dominant language
C
Stars
1.1k
Forks
193
Avg merge
2h 16m
Merged PRs (30d)
2

Description

I need to build and publish the MSIX Core solution so that I can create an installer for older versions of Windows that my users can install from a web page.
I'm following the instructions here
https://docs.microsoft.com/en-us/windows/msix/msix-core/msixcore-clickonce-solution

I have tried to build the MSIX Core 1.1 release solution using Visual Studio 2019 and Visual Studio 2017 as described on the above page but the projects in the solution use the deprecated std::experimental::filesystem namespace. I'm having trouble getting a successful build.
Will there be an update to the MSIX Core solution soon that does not use the deprecated namespace?

Also, the MsixMgrWix project in the MSIXMgr solution is not supported in VisualStudio2017 which is odd because the instructions above use VisualStudio 2017. Perhaps there is a setting in VS2017 I am unaware of that needs to be changed?

Thank you,
Brett Burgeson

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked MSIX Core ClickOnce instructions, then inspect the MSIX Core 1.1 release solution and its use of std::experimental::filesystem. Check the MsixMgrWix project in the MSIXMgr solution using the Visual Studio 2017 and 2019 configurations described. Done means the documented solution builds successfully without the deprecated namespace and the Visual Studio 2017 support discrepancy is explained or documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.