![]() open the latest one and there you will find all your extracted DLLs, which can then be decompiled. The folder will contain randomly named folders. Launch your exe, and a folder with the same name will be created in that location. Which should lead to somewhere similar toĬ:\Users\alenros\AppData\Local\\MyTestApplication If you use windows you can go to c:\Users\ dotPeek64Teleirik Virustotal COMCT元2.dll ComMgr.dll KERNE元2.dll MSVCP90.dll MSVCR90.dll OLEAUT32.dll SHLWAPI.dll USER32.dll mfc90.dll. I wanted to add on Ersönmez's answer, that while ILSpy DotPeek don't support this at the time, since the self-contained single file is just a wrapper that contains all your DLLs and gets extracted on runtime, simply knowing where it is extracted to can save you using ProcMon or ProExp or windbg. ILSpyWin32 This file does not contain a managed assembly. Net 5 states that the way single-file executables will be made would change, so this method will not work for them. ![]() ![]() Update: One of the announcements made regarding. Add an environment variable DOTNET_BUNDLE_EXTRACT_BASE_DIR with the location you want the files extracted to.in the project file add these properties (according to these Microsoft docs):. ![]() ![]() to force it to be unpacked you would need to add the following: Net 5 single-file does not automatically unpack to the same temporary location as before. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |