Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[API Proposal]: Compiled framework-dependent `.exe` should automatically download and install appropriate runtime
See original GitHub issueBackground and motivation
Hey, So I come across a big problem that a lot of people I know complain about: Bundle size of self-contained executables. These can reach upwards of 80 MB for a decently sized app, and that can be a huge problem, more bandwidth use, and entirely removes the benefit of having a shared system runtime that other apps can use.
My proposal is that the compiled framework-dependent executable includes an auto-installer for the runtime, as this would make my (example) 80 MB app just 15-20 MB. AOT and trimming are not always an option, and I would much prefer a shared runtime as .NET is “intended” to be used.
API Proposal
When the user starts the .net .exe, if the runtime is not installed, they should be met with a prompt to automatically install dependencies on the system
API Usage
none
Alternative Designs
No response
Risks
No response
Issue Analytics
- State:
- Created 5 months ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I know the experience has been somewhat lacking in the past, but I think we’ve made some great improvements recently. For example: https://github.com/dotnet/runtime/pull/78087
Moving to installer, as this is more a question of product acquisition. .NET currently doesn’t have a “net installer”