Nothing. The screenshot is meaningless. The story is in the twitter comments underneath. > Both programs want to ensure you only run one copy of themselves. So

Nothing. The screenshot is meaningless. The story is in the twitter comments underneath. > Both programs want to ensure you only run one copy of themselves. So they create a global mutex using the GUID of their .NET assembly, right? > So what happens is that both of them are creating a global mutex to ensure only one copy runs, but instead of basing the GUID on their own code, they're both using the GUID of a part of .NET itself. > And they're using the same one! > Back in 2009, the user "Nathan" asked how to get the GUID of the running assembly. Twelve minutes later, "Cerebrus" answered. And that answer was wrong. > A year and a month later, it was pointed out (by "Yoopergeek") that it gives the wrong GUID. > Three years later, Cerebrus returns and fixes the answer. They can't delete it, because it was accepted > That flawed stackoverflow post is here: https://stackoverflow.com/questions/502303/how-do-i-programmatically-get-the-guid-of-an-application-in-net2-0/502323#502323 https://stackoverflow.com/questions/502303/how-do-i-programm...