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.
Stop adding a runtimeconfig.dev.json by default on built apps
See original GitHub issueProbing consumes a significant ammount of time at startup in the host. With changes introduced in https://github.com/dotnet/runtime/pull/50671, we move away from expensive file-accessing calls made by the host’s probing logic and make them conditional upon whether any additional probing paths were passed to hostpolicy. This improves performance of any dotnet ... command as well as the time to main.
Note that by default the SDK generates a <app>runtimeconfig.dev.json when building an app, which ends up adding additional probing paths which are not necessary (all dependencies are included in the app folder which is probed first, related: #15210) – causing the host to probe more than necessary and missing on any performance gains achieved by the above PR.
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (9 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
Sounds like we want to stop this from happening by default while having some flag if you need this to be generated.
Yes, I think we should turn of the runtimeconfig.dev.json by default. I think we still need it prior to 3.x where we wouldn’t copy referenced NuGet DLLs to the output folder. Also we may still need it if we are using the runtime package store for this line:
"C:\\Users\\daplaist\\.dotnet\\store\\|arch|\\|tfm|",