Quote Originally Posted by justgreat View Post
That's exactly what I want, can you give me an example on how to do that ? and how to use the "/regserver" commad ?
Because I want to make a standalone exe so it will be very usefull that it register itself
You always need an installer. For an ActiveX EXE it takes care of registration either by running the EXE with /regserver or by importing registry settings bundled into the installer package.

See How To Register and Unregister an Out-of-Process COM Component (ActiveX EXE) for help in using the self-reg code VB6 compiles into the program.

In any case it must happen elevated (i.e. with full admin/installer rights). Out of process registration can't be done per-user and must be global.


Quote Originally Posted by justgreat View Post
Me neither, but I have to check and see if in reality it will change or not .. By the way, i won't really make a thread for each file, only for files that I suspect that they will take long time to be treated, for expl, folders that include subfolders and in each lots of files
It doesn't really matter. For what you are trying to do you only want one worker thread that processes requests from your UI thread in sequence. Extra worker threads are very unlikely to buy you much, and beyond about 2 of them there isn't much point.