LS.
On my Win10 PC I have VS 2015 Pro and VS 2013. As of about a week ago I have the weirdest problem.
I create an application in either VS2015 or 2013 (Winform, button => Hello World). It runs fine in VS.
When I go to the debug directory and run the application. I get this blue circle that keeps turning and turning and turning as if it is loading. But nothing happens (not even after 10 minutes).
I opened my Windows logs to see if there where any errors that could help me, no errors where created when I ran my program.
When I use another computer and copy the debug directory to this computer, than it works just fine.
A few days ago I noticed a few times that when I ran the program in Visual Studio, that compiling was a problem.
It mentioned that the file was still in use and that I needed to close that file before I could continue. Closing VS, restarting did the trick. But when I got this error for like the fifth time, that is when I tested to see if it runs all by itself, so not in VS (which it didn't).
I updated VS, I updated Windows (there was some special big update, which failed once but now went OK). I checked for viruses, junk-ware, etc. All was OK. IN general I have no problems with this computer.
The weird part is that I found a work around. If I sign my software (we have a sign tool and a certificate) than there is no problem!! Than it runs.
Of course this never was the case, to my knowledge I did not change anything in my windows that would account for this behaviour.
UAC is something I have turned off for a very long time. I saw on the internet where someone had a problem that looked a bit like mine and he turned off SmartScreen (I remembered that SmartScreen did ask me some question a few days back, probably due to an update). Anyhow I now turned that off as well and it didn't make any difference.
By the way with regards to UAC it doesn't matter whether I create an application that need elevated privileges or not. The problem is the same. To my knowledge, besides some updates nothing really happened to my PC.
And although I am happy that I can do some test after I just sign my executable, it is not ideal (especially as this signature program is installed on a different computer.
I was wondering does anyone ever had a problem like this before and how did he or she overcome this? Doen anyone have a good idea what I could do?
Personally I think the problem is caused by Windows (but what setting in Windows could cause this behaviour). And to make it weirder applications that I developed in VS like a year ago and that are not signed have no problem. Software that I bought from other developers have no problem.
PS I just tested to see if turning of my antivirus made any changes and it didn't ( I have Avast AV free edition and I disabled it completely for like 10 minutes and in that period I tested it, and it made no difference). The only thing I noticed is that the blue loading circle now isn't visible, but that might be a coincidence. Nothing happens (not even an error message).
Weird, weird weird.
I hope someone will give me some idea as to how to solve this.
Kind regards,
Clemens Linders