When I press F11 I just see Running then Debugging for a second in Visual Studio Title bar and then Visual Studio returns back to editing mode. No error no nothing.
Start it once with Windows Explorer, then, while it is running, start a debug session in VS2005 and step through the source code to see where it quits.
Good,
the problem reproduces in the debugger. Sorry, I don't know what
F11 does. Try to get the debugger to break on the first line of
user code by clicking Debug + Step Into. If that works, keep
going with Debug Step Into/Over until you find the statement that
causes the exit. If it doesn't break, we've got an entirely
different kind of problem...
Darned,
I was afraid of that. Tell us more: what language are you
developping in Do you use any DLLs that are implicitly bound to
the .EXE Try to use Dependency Walker on the EXE to see what
other DLLs might be referenced. Use its Profile command to run
the EXE and see how far it gets. If it doesn't make any sense,
post the content of the trace pane to this thread.
multiple instance application?
Sriram Rajamanuri
Andrej
Marco72463
GreyGallon
sameerTripathi
Fakhar Khan
locknload
Juan Pablo Gil
Robert Belka
You can do that by loading the application in different processes.
Thanks,
Suresh.
Johann6879
Jonathas Oliveira