Comments by Russell^' (Top 6 by date)

I love you!

HiSorry, I am not so expert on this kind of stuff.

I will try to explain better but googling it looks that many have the same problem.

The setup project takes the output of my application project.
It Stores into the "application folder" also another exe (not mine).
Then I am simply using a custum action in my setup project to run the other exe.
That exe is the setup of some needed drivers that needs to be installed before that my application runs.

What happens is that the setup fails when run. If UAC is disable the setup succeses.

What do you mean with "that installer should prompt trigger the UAC again"? Cna you please explain better? How to do that?

Thank you
Finally I found a way to export all the memory-cleaning into the distructor of the class I created to contain the thread. So the memory leaks is solved.
It remains a mistery how to detect the right moment to close myself the thread because I found that it can be 'terminated' at any time when the main window of the application is closed.
I think the only way can be now to receive a special call from the exe when it is receiving WM_CLOSE or something like that.
But in my case I don't like this because I want that the thread remains an hidden 'concept' into the dll so I don't like this needing. So I have adapted the code of the thread trying to avoid big problems ... but some little problems with the file managing still remains (I'll solve in future).
Regards

HiIt is a simple worker thread (only file managing). It has to run always during the program run. Then I need to stop it correcly using a simple flag when the program stops.
I am trying to get some event from the CWinApp inside the dll (not the one in the exe, MFC application) to set that flag and wait that the thread exits itself, but it looks that everytime it is too late and the thread is already destroyed from somewhat before.