Application runnig problem.. [modified]
-
I think i have written my guestion hasty. My new application works normal in my laptop. And have installed here Visual Studio 2005. But when i'm copying this application to another one (computer)there appears this message "The Application has faild to start because the Application configuration is incorrect. Reinstalling the application may fix this problem." and now i have find some info from code project. But i cann't do this. There must instal Windows installer 3.0 and .... My guestion : How can i use my application in another computer. What am i install additionally ? May be *.dll files, or *.msi files. ????????? Thanks ! -- modified at 13:10 Friday 19th October, 2007
It's so because on another's computer the workarounds of yours application is different then on yours PC. When compiling, application is compiled with other files (like .dll's for example) and it can be linked with yours application as static or shared... What I'm trying to tell you is that yours application is missing some file on another's computer to work! Try to find out which one, or post more details here!
-
First thing you have to do is distribute the release version of your program. Then, with your application, you need to distribute vcredist_x86.exe and execute it on the target machine. This can be found here[^]. This will install the C run-time library and the MFC libraries. If that still doesn't work, then your application depends on other dll's that are not found. Use dependency walker to check which dll's are required to be distributed with your app.
Cédric Moonen Software developer
Charting control [v1.2]I have checked my program in a computer without visual studio, with debug version crashed because how missing dlls, but release worked good. But now, with your answer. The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
-
I have checked my program in a computer without visual studio, with debug version crashed because how missing dlls, but release worked good. But now, with your answer. The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Which Compiler are you using.. since in Visual Studio 2005, you required to deploy Manifest file needed to run VC++ application !
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixturecheers, Alok Gupta VC Forum Q&A :- I/IV Support CRY- Child Relief and You
-
I have checked my program in a computer without visual studio, with debug version crashed because how missing dlls, but release worked good. But now, with your answer. The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Nelek wrote:
The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
The debug version will never work, even if you run vcredist_x86.exe on the target computer (it only install the release versions of the libraries). Now, you could avoid to distribute this executable if you statically link to the C run-time library and to the MFC dll's (but I'm not 100% sure because I never tested it).
Cédric Moonen Software developer
Charting control [v1.2] -
I have checked my program in a computer without visual studio, with debug version crashed because how missing dlls, but release worked good. But now, with your answer. The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Can you more explain some detaily of your program?
-
Which Compiler are you using.. since in Visual Studio 2005, you required to deploy Manifest file needed to run VC++ application !
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixturecheers, Alok Gupta VC Forum Q&A :- I/IV Support CRY- Child Relief and You
-
Can you more explain some detaily of your program?
But a third party dll, all are things from MFC, list, objects, views... nothing really special
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
-
Nelek wrote:
The question is... Should the release version of a normal MFC-Win32 program work in all computers (supposing no dll is used at all)? Or better include this vcredist_x86 in all applications?
The debug version will never work, even if you run vcredist_x86.exe on the target computer (it only install the release versions of the libraries). Now, you could avoid to distribute this executable if you statically link to the C run-time library and to the MFC dll's (but I'm not 100% sure because I never tested it).
Cédric Moonen Software developer
Charting control [v1.2]Cedric Moonen wrote:
Now, you could avoid to distribute this executable if you statically link to the C run-time library and to the MFC dll's (but I'm not 100% sure because I never tested it).
I statically link all the time and you are correct - you do not need vcredist_x86.exe if you statically link. Judy
-
thanks my friends. I have found. And now application is working very good :) . Bye - - - - - - - - - - - - - - - - - - - -- - - I think i have written my guestion hasty. My new application works normal in my laptop. And have installed here Visual Studio 2005. But when i'm copying this application to another one (computer)there appears this message "The Application has faild to start because the Application configuration is incorrect. Reinstalling the application may fix this problem." and now i have find some info from code project. But i cann't do this. There must instal Windows installer 3.0 and .... My guestion : How can i use my application in another computer. What am i install additionally ? May be *.dll files, or *.msi files. ????????? Thanks ! ;P Avazov
-
VC++ 6.0
Greetings. -------- M.D.V. If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you ;)
Nelek wrote:
VC++ 6.0
In that case, things are even more simple: you just need to distribute your executable and the dll on which it depends. If you statically link to all the dlls, you can just distribute your exe.
Cédric Moonen Software developer
Charting control [v1.2]