Daerynsura
New member
- Joined
- May 14, 2015
- Messages
- 1
- Programming Experience
- 10+
This is a bit of a head scratcher that I can't quite figure out.
My application is using .NET 3.5, targeting Any CPU. When I launch the application through Visual Studio (debug or release), it's fine. When I run the executable, it launches two instances of the application: One of which shows to be using 100K of memory. When you close the application, the second one then appears.
I've tried changing the .NET version (even though I need it to be 3.5 in this particular instance), making it a 1-instance application, and targeting x86 and x64 specifically.
Has anyone had anything like this happen? Does anyone even know where to start to track this down? Any help would be greatly appreciated!
My application is using .NET 3.5, targeting Any CPU. When I launch the application through Visual Studio (debug or release), it's fine. When I run the executable, it launches two instances of the application: One of which shows to be using 100K of memory. When you close the application, the second one then appears.
I've tried changing the .NET version (even though I need it to be 3.5 in this particular instance), making it a 1-instance application, and targeting x86 and x64 specifically.
Has anyone had anything like this happen? Does anyone even know where to start to track this down? Any help would be greatly appreciated!