Compile and run improvement

David Maruca · March 05, 2011, 09:12:57 AM

UAC in Win7 and server 2008 will lock an executable for a period of time after it's run and closed. Even if UAC is turned off. This makes frequent compiling while developing a major pain because sometimes it seems like I have to wait for 1+ minutes.

How about having Compile and Run compile to a Temp####.exe and having the build button build the code into the final exe name?

Any better ideas? I'm about to vmware XP because this bugs me so much.

Jim Dunn · March 05, 2011, 12:52:23 PM

I've never seen this problem on my machine.

I have Win 7, had UAC on, now UAC is off...

But I'm able to compile/run/exit/compile/run/exit/compile/run/exit/... no problem.

Might be your Anti-Virus IDS

David Maruca · March 05, 2011, 03:21:51 PM

I don't understand... this has been pestering me for months, and now I post about it here and it's not doing it anymore. No antivirus is installed. Maybe it will do it again later. /shrug

David Maruca · March 05, 2011, 03:34:17 PM

That means the tech support here is that good!! No, seriously this was happening on fresh installs of 2008r2 and win7 home. I'm glad it's not happening to me now, but it's something to definitely keep in mind when designing software in the future. Any kind of updater, compiler, or whatever is going to have problems.

FYI not a pirate copy. totally legit.

David Kenny · March 05, 2011, 04:28:12 PM

I have a similar issue with compiling. My problem is that I might have left the last compiled executable running when i try to compile again. I get the FF dialog "Abort Compile" letting me know I left the other one running.

Can we have an extra button or two on that dialog? "Close and Recompile" and perhaps "Terminate and Recompile"

Of course, "Close" would ask it nicely to shut down so that it can save what it was doing, release resources, etc. "Terminate" would be more forceful, should the application be hung and unable to close on its own.

David

Haakon Birkeland · March 05, 2011, 06:36:47 PM

It's an occasional problem on XP Pro x64 as well. A real bother that I solve with LockHunter.

Douglas McDonald · March 14, 2011, 02:33:51 PM

I've never had this problem. My UAC is Off.

Doug

Roger Garstang · March 17, 2011, 12:25:11 PM

I'd blame antivirus before UAC. 9 times out of 10 my AV keeps something open scanning it. It may even look like Explorer holding it since they work inline with file access, etc. May try telling it to ignore/not check that folder.

David Maruca · March 17, 2011, 12:51:04 PM

No antivirus installed.

Haakon Birkeland · March 17, 2011, 01:32:43 PM

QuoteNo antivirus installed.

You see â€" no antivirus, no problems! Just like on the Mac. 8oÃž

David Maruca · March 17, 2011, 01:56:31 PM

Quote from: Haakon Birkeland on March 17, 2011, 01:32:43 PM
You see â€" no antivirus, no problems! Just like on the Mac. 8oÃž

haha that's hilarious.

Roger Garstang · March 17, 2011, 02:08:30 PM

I could see that on a Mac or Linux just because they are used less and have fewer virus issues...there are still virus out there to infect them. But, I'd never leave a Windows box wide open. UAC may protect a little, but it was stated this is now off, and I wouldn't trust it much anyway being from M$. In the end, no AV protection could be the problem. Without knowing there is nothing malicious running there could be something accessing your files and perhaps even infecting them...especially since they are exe. Windows itself won't keep them open any longer than told. Are you sure there is no built-in Microsoft protection or bitlocker causing issues. I know they have a couple of their own programs now that keep insisting to install during update. Maybe they got installed without you knowing or were pre-installed either by MFG or during Windows Setup?