New
#31
Hi all,
I'm the developer of this utility. I'm glad to see that you like it! I saw this forum when checking out some of the recent referring URLs and I just wanted to address the concerns over the application's TCP status in process explorer.
The .NET Framework 2.0 includes a feature called the "Application Framework", this feature makes development easier by automatically handling some of the more tedious (and boring!) programming tasks required for certain program behavior.
The framework was enabled for Flip 3D Activator to make it easier to enforce a "single instance" of the utility. (To avoid any mess from having two or more Flip 3D Activators trying to activate flip 3d)
Enabling this framework enables something called remoting (not just for this reason, but for others as well), which is a way for processes to communicate with each other. One of the easiest ways to accomplish this is through local-only TCP connections (hence the "listening"). It is listening for a new instance of the application to tell the current instance that a new instance was launched, just in case we need to handle that for some reason. (We don't, other than telling the new instance to exit.)
I hope this clears it up!
-N
That makes sense, thanks for letting us know Noty.