Comments by dimaba10000 (Top 8 by date)

The extraction library I use is, DotNetZip... I have compared it to Shell32, 7zip, and CMD extraction. DotNetZip was the fastest.

Well of what I am aware... The extraction consumes the largest amount of time.

My product (mod installer) is quite popular in a gaming community and there are a few videos on YouTube where our fans posted guides on how to use the installer.

Most of them would get stuck at the extraction part for around 20 seconds... Some longer. I am guessing it depends on their computer configurations.

I will post code snippets in the thread right now! Give me around 5 - 7 minutes.

Incorrect. I do not delete the %temp% files.

The only "temporary files" I delete, are the ones that the program places on the computer.

For example... The .zip file.

Well, you defiantly have a point here! But you are throwing so much information at me at the same time... I can't really understand where to start from. My original question was, if it was possible to get my executable application to check for .dll files in a specific folder on the users computer, to use that .dll file as a reference. Since I don't want to keep both .dll and .exe in the same folder.

Here is something I'm thinking of doing:

I will keep the .dll inside the Resources folder, once the .exe will be executed, it will copy the .dll into ProgramFiles or Temp or even AppData (just anything). Then the program will look in that folder for the .dll and use it as a reference (DotNetZip) to be able to extract files I need.

I thank you very much!