Hallo,
Why is there a difference between pressing the .EXE file created by visual studio and running the file from visual studio itself? When I press the .exe file the program crashes, but when I press the exe file in the folder the program crashes.
Hallo,
Why is there a difference between pressing the .EXE file created by visual studio and running the file from visual studio itself? When I press the .exe file the program crashes, but when I press the exe file in the folder the program crashes.
There shouldn't be much of a difference at all; at most, I think, VS will add a little bit of code to make sure the command window stays open. Any run-time error will happen either way.
That doesn't sound like a difference.
The only difference between launching from VS and launching from the command line or the explorer is the working directory. VS will give you the project root as the working directory, while direct execution gives you the program's own directory. If your program does not correctly check results of file open operations, it may crash as a result of not being able to open a file.
So if I run it from visual studio I can do this:
while if I run it from a folder I have to do:Code:Openfile("Data\house.jpg);
Also, when I run an other project I get an vector error, but it works fine if I press F5 in visual studioCode:Openfile("C:\programFiles\VS\myProject\Data\house.jpg")
It's a bug that happens when certain conditions are met, which aren't met when running it via Visual Studio.
You need to re-create those conditions. For example, the path.
Within a string literal, the backslashes should generally be escaped; i.e.Quote:
Originally Posted by h3ro
(I simply prefer forward slashes.)Code:Openfile("C:\\programFiles\\VS\\myProject\\Data\\house.jpg")
Are you checking the return value of Openfile?
I know, but I typed the openfile() function while I was making the post and forgot about it. In my program I use an other function, where I use \\ and it returns a bool.Quote:
Within a string literal, the backslashes should generally be escaped; i.e.
Code:
Openfile("C:\\programFiles\\VS\\myProject\\Data\\h ouse.jpg")
(I simply prefer forward slashes.)
Are you checking the return value of Openfile?
Thanks for the replies so far, but I still dont fully understand why pressing the .exe causes the program to fail.
Well, have you told us how it fails yet?
I have tried, but it might not be that easy to find between all my other random writing, sorry about that.
I have two different .exe files (two versions of the same project) which work when I run them through visual studio, but fails when I press the .exe file in the folder.
The first .exe file brings up the "this program has preformed an illegal operation and will now be closed window". No other information is given.
The second .exe file brings up an error that there is an vector out of range in my program.
The weird thing is that they both work fine when running from Visual studio.
Some additional info about the project:
* I am reading from several different files, all located inside the project folder.
* I am linking to static libraries
Command line arguments?
Are you sure you are running the same executable (e.g. you may be building a debug version, and then running the release version, or other way around - I've made that mistake more than once!)
--
Mats
Im not at home now, so im not sure, but i assume its what ever is default as I have not changed anything apart from linking to one libary.Quote:
Command line arguments?
It happens in both debug and release.Quote:
Are you sure you are running the same executable (e.g. you may be building a debug version, and then running the release version, or other way around - I've made that mistake more than once!)
If I go back to a really really old version of the project I can run it from the .exe file, so it has to be something to do with my code. I just dont understand why and how