Build as Self Contained and Selfhost CefSharp SubProcess #947

New Issue

MrUnknownDE · 2026-04-05T16:37:26+02:00

MrUnknownDE commented

2026-04-05 16:37:26 +02:00

Originally created by @DubyaDude on 11/22/2023

This changes the build of VRCX to be self-contained, removing the requirement of installing dotnet, and not having to deal with potential bad dotnet installs.

Pros

No longer dependent on user-installed dotnet runtime.
Closes #695 - FIxes bad dotnet installs causing a download loop.

Cons

Larger Installer - The installer increased from 161MB to 227MB
Larger install - The VRCX folder after the first launch went from 356MB to 516MB
More files - The VRCX folder after the first launch went from 992 files to 1,450

Pro/Con

We are distributing our own runtime now. This allows for much better control of the runtime the app runs off possibly reducing the 'Works on my machine' type of issues. However, this means the responsibility of keeping the runtime up to date now falls on us developers rather than the end-user. (NOTE: because of the GitHub runner publishing builds, runtime will be automatically upgraded to the latest patch version the runner has, which is pretty kept up to date)

Not Changed

CPU or RAM usage has not been significantly affected.

*Originally created by @DubyaDude on 11/22/2023* This changes the build of VRCX to be self-contained, removing the requirement of installing dotnet, and not having to deal with potential bad dotnet installs. Pros - No longer dependent on user-installed dotnet runtime. - Closes #695 - FIxes bad dotnet installs causing a download loop. Cons - Larger Installer - The installer increased from 161MB to 227MB - Larger install - The VRCX folder after the first launch went from 356MB to 516MB - More files - The VRCX folder after the first launch went from 992 files to 1,450 Pro/Con - We are distributing our own runtime now. This allows for much better control of the runtime the app runs off possibly reducing the 'Works on my machine' type of issues. However, this means the responsibility of keeping the runtime up to date now falls on us developers rather than the end-user. (NOTE: because of the GitHub runner publishing builds, runtime will be automatically upgraded to the latest patch version the runner has, which is pretty kept up to date) Not Changed - CPU or RAM usage has not been significantly affected.

MrUnknownDE closed this issue

2026-04-05 16:37:26 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#947