Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Self-contained releases #390

Open
epollockSPEAR opened this issue Jan 19, 2025 · 1 comment
Open

[Feature]: Self-contained releases #390

epollockSPEAR opened this issue Jan 19, 2025 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@epollockSPEAR
Copy link

Expected behavior

.NET has a build feature to make a self-contained release, so that there isn't an external dependency on the framework. This could be really nice when, like me, you're trying to launch it via Proton -> MO2. That arrangement doesn't seem able to see the runtimes no matter what I do.

other

No response

@epollockSPEAR epollockSPEAR added the enhancement New feature or request label Jan 19, 2025
@BrotherErryn
Copy link

(Original post was my work account by mistake)

I just cloned the repo, added these to the PropertyGroup:

<PublishSingleFile>false</PublishSingleFile>
<SelfContained>true</SelfContained>

...then did a publish of the project. The program now launches normally from MO2 inside Proton instead of being unable to find the DOTNET runtimes.

Maybe an additional build for a release could do this?

@Monitor221hz Monitor221hz self-assigned this Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants