[GH-ISSUE #1380] [Feature Request] Consider enabling <RollForward>major</RollForward> for ScreenToGif.exe #3623

New issue

Closed

opened 2026-03-01 19:14:07 +03:00 by kerem · 0 comments

kerem commented 2026-03-01 19:14:07 +03:00

Owner

Copy link

Originally created by @nil4 on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1380

Originally assigned to: @NickeManarin on GitHub.

Is your feature request related to a problem? Please describe.

ScreenToGif currently targets net8.0:

github.com/NickeManarin/ScreenToGif@998e61923b/ScreenToGif/ScreenToGif.csproj (L3)

Trying to start ScreenToGif.exe on a machine where a later version (e.g. .NET 9) is installed, but .NET 8.x is not installed, currently fails. The rather unfortunate "You must install or update .NET to run this application" dialog appears and the program is blocked from launching:

Describe the solution you'd like

Consider adding <RollForward>major</RollForward> to ScreenToGif.csproj so that future releases do not need this workaround, and ScreenToGif.exe starts on .NET 8 or any later major versions out of the box.

ref. https://learn.microsoft.com/en-us/dotnet/core/versions/selection#control-roll-forward-behavior

Describe alternatives you've considered

End-users can resort to a rather clunky, but working, workaround -- define a batch file to set the roll-forward policy via an environment variable, e.g.

set DOTNET_ROLL_FORWARD=major
ScreenToGif.exe

This solves the issue of launching correctly with a later .NET runtime available, but should not be necessary if the roll-forward policy is defined in the project file. Doing that would allow ScreenToGif.exe to start on .NET 8, 9 or any later version.

Additional context

ref. https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#rollforward

Originally created by @nil4 on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1380 Originally assigned to: @NickeManarin on GitHub. **Is your feature request related to a problem? Please describe.** ScreenToGif currently targets `net8.0`: https://github.com/NickeManarin/ScreenToGif/blob/998e61923bf4572482e7fac9a3a0abf970cc147a/ScreenToGif/ScreenToGif.csproj#L3 Trying to start `ScreenToGif.exe` on a machine where a later version (e.g. .NET 9) is installed, but .NET 8.x is not installed, currently fails. The rather unfortunate "*You must install or update .NET to run this application*" dialog appears and the program is blocked from launching:  **Describe the solution you'd like** Consider adding `<RollForward>major</RollForward>` to `ScreenToGif.csproj` so that future releases do not need this workaround, and ScreenToGif.exe starts on .NET 8 **or any later major versions** out of the box. ref. https://learn.microsoft.com/en-us/dotnet/core/versions/selection#control-roll-forward-behavior **Describe alternatives you've considered** End-users can resort to a rather clunky, but working, workaround -- define a batch file to set the roll-forward policy via an environment variable, e.g. ```cmd set DOTNET_ROLL_FORWARD=major ScreenToGif.exe ``` This solves the issue of launching correctly with a later .NET runtime available, but should not be necessary if the roll-forward policy is defined in the project file. Doing that would allow `ScreenToGif.exe` to start on .NET 8, 9 or any later version. **Additional context** ref. https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#rollforward

kerem 2026-03-01 19:14:07 +03:00

• closed this issue
• added the
  🔷Enhancement
  ⬜ Completed
  labels

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dev

v2.40

2.43.1

2.43

2.42.1

2.42

2.41.5

2.41.4

2.41.3

2.41.2

2.41.1

2.41

2.40.1

2.40

2.39

2.38.1

2.38

2.37.2

2.37.1

2.37

2.36

2.35.4

2.35.3

2.35.2

2.35.1

2.35

2.34.1

2.34

2.33.1

2.33

2.32.1

2.32

2.31

2.30.1

2.30

2.29.1

2.29

2.28.2

2.28.1

2.28

2.27.3

2.27.2

2.27.1

2.27

2.26.1

2.26

2.25

2.24.2

2.24.1

2.24

2.23.2

2.23.1

2.23

2.22.1

2.22

2.21.2

2.21.1

2.21

2.20.4

2.20.3

2.20.2

2.20.1

2.20

2.19.3

2.19.2

2.19.1

2.19

2.18

2.17.1

2.17

2.16

2.15.2

2.15.1

2.15

2.14.1

2.14

2.13.3

2.13.2

2.13.1

2.13

2.12.1

2.12

2.11

2.10

2.9

2.8.1

2.8

2.7.3

2.7.2

2.7.1

2.7

2.6

2.5

2.4

2.3.2

2.3.1

2.3

2.2

2.1

Labels

Clear labels   

copy cats

  

duplicated

  

future feature

  

pull-request

Mirrored from GitHub Pull Request

  

⬜ Accepted

  

⬜ Completed

  

⬜ Help Wanted 💪

  

⬜ In Progress

  

⬜ Missing Details

  

⬜ Pending

  

⬜ Waiting For Answer ⏳

  

🆕 feature preview

  

🔷 Bug 🐛

  

🔷 Out Of Scope

  

🔷 Out Of Scope

  

🔷 Question

  

🔷Enhancement

  

🔷Enhancement

  

🔷Invalid / External

  

🔷Knowledge Base

  

🔷Won't Fix

  

🕑 High

  

🕑 High

  

🕑 High

  

🕕 Medium

  

🕙 Low

  

🕛 Critical

No labels

copy cats

duplicated

future feature

pull-request

⬜ Accepted

⬜ Completed

⬜ Help Wanted 💪

⬜ In Progress

⬜ Missing Details

⬜ Pending

⬜ Waiting For Answer ⏳

🆕 feature preview

🔷 Bug 🐛

🔷 Out Of Scope

🔷 Out Of Scope

🔷 Question

🔷Enhancement

🔷Enhancement

🔷Invalid / External

🔷Knowledge Base

🔷Won't Fix

🕑 High

🕑 High

🕑 High

🕕 Medium

🕙 Low

🕛 Critical

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#3623

No description provided.