Dependency injection and configuration abstractions and logging extensions and whatever else may make things easier on the programming side, but they're big scary words to the average end-user who thinks he's getting something simple.
The less noise to sort through in the root folder, the less stress there is on the end user to find the executable, and the less in-your-face complexity is shown for what is (or should be) viewed as a simple program. Primarily it's about the end-user experience for an xcopy deployment. config element seems like a relatively trivial change, but would require the addition of a new property, which is probably less desirable than making use of the existing information in deps.json. It's only the loading part on program run that's out of my hands.Īlternatively, the option for a property analogous to the original. If those files could be placed there automatically on build or publish, that would be a nice convenience, but it can be done as a post-build event on my end, so is not necessary for the time being. It would be a mild annoyance to make sure everything is in the right place, but the deployment would be clean. I'd just need to create one additional subdirectory level and move files into that, as well as handle files that go into different subdirectories (eg: "lib/netcoreapp3.0/"). The relative paths in that file (eg: "lib/netstandard2.0/HtmlAgilityPack.dll") are fine as a subdirectory of the root folder. The deps.json file wouldn't actually need to be modified. I'm saying that the individual files are already tiny in size, so I'm not wanting to go a route that negates that (ie: a single exe or self-contained), but that it's not desirable to have them all in the root folder. Why is it important to have small file size in the root folder, but it's OK to have the rest in a subfolder?
Use a custom native host which can specify additional probing paths to the runtime by modifying the APP_PATHS runtime property.deps.json (not sure if SDK has a good way to do this though) and implementing a handler for the event where you find them manually. Just to list other options, not that I would recommend either: deps.json or SDK support (ideally SDK support).
#MEDIACODER X64 OUTPUT FOLDER TO ORIGINAL MANUAL#
If there's enough interest I'm not opposed to somehow tweaking the host to make this work - but it would still require either manual modification of the.
#MEDIACODER X64 OUTPUT FOLDER TO ORIGINAL CODE#
I don't know the exact reason why the code works that way unfortunately (it's been like that for a long time). deps.json to point to the files in the subfolder, unfortunately this is currently broken in the host (for searches done in the app folder, the relative path specified is ignored). The ideal solution would be to modify the. But then again even if you move some files into subfolder the entire app is still the same size, so you're not going to save any size issues with this approach.
0 kommentar(er)
