Release build doesnt function completely on other systems
-
Hello all, I recently compiled a release build of a project and ran into initial problems that would cause the application to fail. After correcting these problems (program appears to function properly w/ no crashes), I decided to send it to some friends to test out. On the first attempt, my friend reported he receive a msg asking for MSVCPP70. Thinking that this might be a MFC dll issue i went into my project settings and set the option to use mfc in a static library. After doing this, my program will run, except for a feature which communicates w/ a server via a worker thread. The odd thing is... the application runs flawlessly on my own system. What issues do you think I am running into? Are there dlls that i should be coupling w/ my release build?
-
Hello all, I recently compiled a release build of a project and ran into initial problems that would cause the application to fail. After correcting these problems (program appears to function properly w/ no crashes), I decided to send it to some friends to test out. On the first attempt, my friend reported he receive a msg asking for MSVCPP70. Thinking that this might be a MFC dll issue i went into my project settings and set the option to use mfc in a static library. After doing this, my program will run, except for a feature which communicates w/ a server via a worker thread. The odd thing is... the application runs flawlessly on my own system. What issues do you think I am running into? Are there dlls that i should be coupling w/ my release build?
Knave* wrote: What issues do you think I am running into? It's hard to say from the info you provide... Knave* wrote: my program will run, except for a feature which communicates w/ a server via a worker thread So, what happens with that feature? Does it give some error (which)? -- jlr http://jlamas.blogspot.com/[^]
-
Hello all, I recently compiled a release build of a project and ran into initial problems that would cause the application to fail. After correcting these problems (program appears to function properly w/ no crashes), I decided to send it to some friends to test out. On the first attempt, my friend reported he receive a msg asking for MSVCPP70. Thinking that this might be a MFC dll issue i went into my project settings and set the option to use mfc in a static library. After doing this, my program will run, except for a feature which communicates w/ a server via a worker thread. The odd thing is... the application runs flawlessly on my own system. What issues do you think I am running into? Are there dlls that i should be coupling w/ my release build?
Knave* wrote: MSVCPP70 :confused: Check the dll's used with Dependency Walker. ... she said you are the perfect stranger she said baby let's keep it like this... Tunnel of Love, Dire Straits.
-
Hello all, I recently compiled a release build of a project and ran into initial problems that would cause the application to fail. After correcting these problems (program appears to function properly w/ no crashes), I decided to send it to some friends to test out. On the first attempt, my friend reported he receive a msg asking for MSVCPP70. Thinking that this might be a MFC dll issue i went into my project settings and set the option to use mfc in a static library. After doing this, my program will run, except for a feature which communicates w/ a server via a worker thread. The odd thing is... the application runs flawlessly on my own system. What issues do you think I am running into? Are there dlls that i should be coupling w/ my release build?
Sounds more like a firewall/network problem to me. Where is the server located? Is it accesible from your friend's PC?