Visual Studio 2008 c++ Executable (Debug and Release) not working
-2
hope someone can help.
I'm currently writing a 2D game engine in c++. When I run the application from within Visual Studio 2008 using either debug or release all goes fine.
When I then run the executable files (either debug or release) from Windows Explorer, neither work and just display a blank Window.
Does anyone know what is causing this?
- Load project into VS 2008
- Change configuration to "Debug"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[16672] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Debug folder in project.
- Run executable, blank window is shown.
- Change configuration to "Release"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[18872] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Release folder in project.
- Run executable, blank window is shown.
c++ visual-studio-2008 executable
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
|
show 16 more comments
-2
hope someone can help.
I'm currently writing a 2D game engine in c++. When I run the application from within Visual Studio 2008 using either debug or release all goes fine.
When I then run the executable files (either debug or release) from Windows Explorer, neither work and just display a blank Window.
Does anyone know what is causing this?
- Load project into VS 2008
- Change configuration to "Debug"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[16672] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Debug folder in project.
- Run executable, blank window is shown.
- Change configuration to "Release"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[18872] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Release folder in project.
- Run executable, blank window is shown.
c++ visual-studio-2008 executable
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
1
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24
|
show 16 more comments
-2
-2
-2
0
hope someone can help.
I'm currently writing a 2D game engine in c++. When I run the application from within Visual Studio 2008 using either debug or release all goes fine.
When I then run the executable files (either debug or release) from Windows Explorer, neither work and just display a blank Window.
Does anyone know what is causing this?
- Load project into VS 2008
- Change configuration to "Debug"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[16672] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Debug folder in project.
- Run executable, blank window is shown.
- Change configuration to "Release"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[18872] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Release folder in project.
- Run executable, blank window is shown.
c++ visual-studio-2008 executable
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
hope someone can help.
I'm currently writing a 2D game engine in c++. When I run the application from within Visual Studio 2008 using either debug or release all goes fine.
When I then run the executable files (either debug or release) from Windows Explorer, neither work and just display a blank Window.
Does anyone know what is causing this?
- Load project into VS 2008
- Change configuration to "Debug"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[16672] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Debug folder in project.
- Run executable, blank window is shown.
- Change configuration to "Release"
- Click the "Start Debugging" button
- Application compiles and builds, all is ok
- Application runs, all is ok
- Close Application
- Output window in VS shows "The program '[18872] Mouse Engine v2.exe: Native' has exited with code 0 (0x0)."
- Open Windows Explorer window and locate executable file from the Release folder in project.
- Run executable, blank window is shown.
c++ visual-studio-2008 executable
c++ visual-studio-2008 executable
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
edited Nov 12 '18 at 13:04
Ken Allen
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
asked Nov 12 '18 at 12:06
Ken AllenKen Allen
13
13
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
1
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24
|
show 16 more comments
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
1
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
1
1
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24
|
show 16 more comments
2 Answers
2
active
oldest
votes
0
Some things to look for are missing dependencies such as config files and data files that your program can't find.
You can also try Dependency Walker to make sure all your dll's are available. http://www.dependencywalker.com
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
add a comment |
0
There are a few things to check to resolve this sort of problem.
- Check all variables are initialised. Seems obvious but this can be crucial. I found best way to solve this is to #DEFINE _LOG at start and output variable values to a log file in each function using #IFDEF _LOG. This way you can turn it on or off.
- If your application is just a blank window, check if it is running (using CPU time). This is a good indication that something is preventing it to find any image or font files.
- Check that the Debug or Release folder structure matches that within your project folder to ensure links to files and textures work.
- Make sure in project preferences to set the Runtime Library entry to Multi-threaded (/MT). This should make your application less dependent on additional dll’s.
- Check for problems in your code. See point 1 with using log files to help with this.
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261860%2fvisual-studio-2008-c-executable-debug-and-release-not-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Some things to look for are missing dependencies such as config files and data files that your program can't find.
You can also try Dependency Walker to make sure all your dll's are available. http://www.dependencywalker.com
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
add a comment |
0
Some things to look for are missing dependencies such as config files and data files that your program can't find.
You can also try Dependency Walker to make sure all your dll's are available. http://www.dependencywalker.com
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
add a comment |
0
0
0
Some things to look for are missing dependencies such as config files and data files that your program can't find.
You can also try Dependency Walker to make sure all your dll's are available. http://www.dependencywalker.com
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
Some things to look for are missing dependencies such as config files and data files that your program can't find.
You can also try Dependency Walker to make sure all your dll's are available. http://www.dependencywalker.com
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
answered Nov 12 '18 at 16:25
Michael SuretteMichael Surette
494110
494110
add a comment |
add a comment |
0
There are a few things to check to resolve this sort of problem.
- Check all variables are initialised. Seems obvious but this can be crucial. I found best way to solve this is to #DEFINE _LOG at start and output variable values to a log file in each function using #IFDEF _LOG. This way you can turn it on or off.
- If your application is just a blank window, check if it is running (using CPU time). This is a good indication that something is preventing it to find any image or font files.
- Check that the Debug or Release folder structure matches that within your project folder to ensure links to files and textures work.
- Make sure in project preferences to set the Runtime Library entry to Multi-threaded (/MT). This should make your application less dependent on additional dll’s.
- Check for problems in your code. See point 1 with using log files to help with this.
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
add a comment |
0
There are a few things to check to resolve this sort of problem.
- Check all variables are initialised. Seems obvious but this can be crucial. I found best way to solve this is to #DEFINE _LOG at start and output variable values to a log file in each function using #IFDEF _LOG. This way you can turn it on or off.
- If your application is just a blank window, check if it is running (using CPU time). This is a good indication that something is preventing it to find any image or font files.
- Check that the Debug or Release folder structure matches that within your project folder to ensure links to files and textures work.
- Make sure in project preferences to set the Runtime Library entry to Multi-threaded (/MT). This should make your application less dependent on additional dll’s.
- Check for problems in your code. See point 1 with using log files to help with this.
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
add a comment |
0
0
0
There are a few things to check to resolve this sort of problem.
- Check all variables are initialised. Seems obvious but this can be crucial. I found best way to solve this is to #DEFINE _LOG at start and output variable values to a log file in each function using #IFDEF _LOG. This way you can turn it on or off.
- If your application is just a blank window, check if it is running (using CPU time). This is a good indication that something is preventing it to find any image or font files.
- Check that the Debug or Release folder structure matches that within your project folder to ensure links to files and textures work.
- Make sure in project preferences to set the Runtime Library entry to Multi-threaded (/MT). This should make your application less dependent on additional dll’s.
- Check for problems in your code. See point 1 with using log files to help with this.
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
There are a few things to check to resolve this sort of problem.
- Check all variables are initialised. Seems obvious but this can be crucial. I found best way to solve this is to #DEFINE _LOG at start and output variable values to a log file in each function using #IFDEF _LOG. This way you can turn it on or off.
- If your application is just a blank window, check if it is running (using CPU time). This is a good indication that something is preventing it to find any image or font files.
- Check that the Debug or Release folder structure matches that within your project folder to ensure links to files and textures work.
- Make sure in project preferences to set the Runtime Library entry to Multi-threaded (/MT). This should make your application less dependent on additional dll’s.
- Check for problems in your code. See point 1 with using log files to help with this.
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
answered Nov 13 '18 at 20:52
Ken AllenKen Allen
13
13
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261860%2fvisual-studio-2008-c-executable-debug-and-release-not-working%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please, improve the wording of your question. As it is it doesn't make sense. (I assume, you can run your application out of VS but you cannot run it standalone (e.g. from Explorer). This might have to do with resolution of dependency DLLs which may fail in the latter case. However, this is not sufficiently answerable without more info from you.)
– Scheff
Nov 12 '18 at 12:09
At a minimum you'd need to show some screen shots of the problem. We can't just guess at the causes in a vacuum! Do you have a history of what changed? (You're using some source control system, I assume?) Have you tried rolling back to last known good configuration?
– Rags
Nov 12 '18 at 12:09
Hi, thanks for reply's. Yes, the application runs fine out of VS (as both debug and release versions). It's when I run the apps standalone from Explorer.
– Ken Allen
Nov 12 '18 at 12:16
1
@Rags No. Screenshots. Ever. Error messages verbatim and stacktraces as text.
– Passer By
Nov 12 '18 at 12:21
Based on your information, it's impossible to be more specific than "it's caused by a bug in your code". Initialise all your variables, and make sure that you're not making any assumptions about the working directory.
– molbdnilo
Nov 12 '18 at 12:24