On Windows and Mac, Visual Studio and VS Code can be used to debug crash dumps. On Linux, the only debugger which can attach to self-contained single-file processes or debug crash dumps is SOS with LLDB. To avoid shipping loose files entirely, consider using embedded resources. NET 6 use the file name from ProcessPath. To find the file name of the executable, use the first element of Environment.GetCommandLineArgs(), or starting with. To access files next to the executable, use AppContext.BaseDirectory. We have some recommendations for fixing common scenarios: Returns a string with the value of or throws an exception. The table below has the relevant runtime library API details for single-file use. The most common cause of problems is dependence on file paths for files or DLLs shipped with the application. If you use a third-party framework or package, it's possible that they may also use one of these APIs and need modification. Some APIs are not compatible with single-file deployment and applications may require modification if they use these APIs. For more information about extraction, see Including native libraries. NET Core 3.x, set the property IncludeNativeLibrariesForSelfExtract to true. To embed those files for extraction and get exactly one output file, like in. On Windows, this means that the managed binaries are embedded in the single-file bundle, but the native binaries of the core runtime itself are separate files. When the app starts, the managed DLLs are extracted and loaded in memory, avoiding the extraction to a folder. NET 5, only managed DLLs are bundled with the app into a single executable. When the app starts, the single file app was extracted to a folder and run from there. NET Core 3.x, publishing as a single file produced exactly one file, consisting of the app itself, dependencies, and any other files in the folder during publish. Single file deployment isn't compatible with Windows 7. The single file deployment option can be combined with ReadyToRun and Trim publish options. The size of the single file in a self-contained application will be large since it will include the runtime and the framework libraries. Single File deployment is available for both the framework-dependent deployment model and self-contained applications. NET Core host first extracts all files to a directory before running the application.NET 5 improves this experience by directly running the code without the need to extract the files from the app. NET Core 3.0, when a user runs your single-file app. This deployment model has been available since. Bundling all application-dependent files into a single binary provides an application developer with the attractive option to deploy and distribute the application as a single file.