microsoft / microsoft/FFmpegInterop

Drop support for Windows 8.1 and WP 8.1 and use VS2017 platform toolkit

Open
#206 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1.4k
Forks
319
PR merge metrics
No merged PRs in 30d

Description

These are really old platforms. Microsoft stopped supporting WP8.1 already, user base on Windows 8.1 is very small and shrinking. I do not think that anyone will start a new project targeting Windows 8.1 or even WP 8.1. Windows 10 is the way to go for all new apps. Let's move on.

Having to maintain these platforms makes adding new features really difficult. Not only would we have to install VS2015 (a whooping 26GB install with all required packages) just to check that they build, but theoretically, we would also have to test new features on Windows 8.1 and even WP 8.1, which is just not feasible anymore.

So I propose to drop support for these platforms for future development. A support branch can be created, so those who still do care about these platforms (anyone there?) can still build it. Project files for Windows 10 version should be updated to use the VS2017 platform toolkit.

Please let me know what you think.

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

Review the Windows project files and current build configuration for references to Windows 8.1, WP 8.1, and the VS2015 platform toolkit. Update the Windows 10 projects to use the VS2017 toolkit, then verify that the supported projects still build and that legacy platform support is removed as proposed.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.