Well, your assumption was right as the error doesn't appear as long as I wait about 5 seconds after closing the application before trying to launch it again. Hence, this seems to be nothing to worry about so you can provide iCopy 1.45 to the public, now :)
If I am allowed to ask one final question, I would like to know why it takes nearly 20 seconds for iCopy to start on a Core 2 Duo machine although the executable is just a few hundred kilobytes in size. I wonder if .NET is the reason why most modern programs often take much longer to show their GUI than older "classic" ones... But this is just out of curiousity as I am quite sure that you can't do anything about that. It would just be good to know if it is really .NET that makes launching modern applications slower.
Thank you very much again for all the kind and perfect support - and all that for a completely free software tool !
Well, your assumption was right as the error doesn't appear as long as I wait about 5 seconds after closing the application before trying to launch it again. Hence, this seems to be nothing to worry about so you can provide iCopy 1.45 to the public, now :)
If I am allowed to ask one final question, I would like to know why it takes nearly 20 seconds for iCopy to start on a Core 2 Duo machine although the executable is just a few hundred kilobytes in size. I wonder if .NET is the reason why most modern programs often take much longer to show their GUI than older "classic" ones... But this is just out of curiousity as I am quite sure that you can't do anything about that. It would just be good to know if it is really .NET that makes launching modern applications slower.
Thank you very much again for all the kind and perfect support - and all that for a completely free software tool !
Sincerely yours
Andreas Hüller