🔒 Locked
distributing vc2k5 express apps?
Advertisement
Original Post
i just tried to run my app on another pc and got the error message "application configuration is incorrect". i found that i'm supposed to distribute some file with my app that installs the required runtimes, but it isn't included with the express edition. anyone care to point me in the right direction?
Quote:
Original post by Oluseyi
I always start by Googling my errors, under the obviously mistaken assumption that I'm not the first person to encounter them.
been there, done that. i included the dll's and i still get this message.
You ran depends.exe?
You included the message in full in your description to a public community so people can stop guessing?
No disrespect intended, but, as is, I have no idea if you actually have a problem, since all I get from you is "application configuration is incorrect," which I presume - and my earlier Google search would seem to confirm - is not the entire error message. The more information you provide, the more help you can receive.
Good luck.
You included the message in full in your description to a public community so people can stop guessing?
No disrespect intended, but, as is, I have no idea if you actually have a problem, since all I get from you is "application configuration is incorrect," which I presume - and my earlier Google search would seem to confirm - is not the entire error message. The more information you provide, the more help you can receive.
Good luck.
running depends.exe on a test pc i get this error:
i've done plenty of searching and all i've found is pages of people having the same problem with no solutions that work.
Quote:
Error: The Side-by-Side configuration information in "c:\documents and settings\evan\desktop\brian\SDLGLFW.EXE" contains errors. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001).
i've done plenty of searching and all i've found is pages of people having the same problem with no solutions that work.
ah, I struggled with just this problem the other day, after a few hours of googling around and hitting my head against solid objects I finally found the solution to the problem [grin]
and for a modest fee I'll share it with you...
oh, all right, I'll tell you for free, coz I'm feeling nice...
You see, the problem is with the new visual studio system MS have changed how you distro dlls. If you want to link to the runtime dlls then you need a manifest file in your application to tell it what dlls to link to, the good news is the IDE handles this for you.
The problem then comes down to how the hell do I distro the dlls?
As you've found out just including them with the app doesnt work, this is because the new loader looks for the dlls in only one location, a certain system location, if it doesnt find them there then it wont load them, so what you have todo is make an installer which will install the correct dlls into this folder so your app will run.
Step forward Nikola Dudar with a web blog of the answer, which if you follow his step by step instructions will work perfectly [smile]
and for a modest fee I'll share it with you...
oh, all right, I'll tell you for free, coz I'm feeling nice...
You see, the problem is with the new visual studio system MS have changed how you distro dlls. If you want to link to the runtime dlls then you need a manifest file in your application to tell it what dlls to link to, the good news is the IDE handles this for you.
The problem then comes down to how the hell do I distro the dlls?
As you've found out just including them with the app doesnt work, this is because the new loader looks for the dlls in only one location, a certain system location, if it doesnt find them there then it wont load them, so what you have todo is make an installer which will install the correct dlls into this folder so your app will run.
Step forward Nikola Dudar with a web blog of the answer, which if you follow his step by step instructions will work perfectly [smile]
Quote:
Original post by phantom
Step forward Nikola Dudar with a web blog of the answer, which if you follow his step by step instructions will work perfectly [smile]
works perfectly! thanks a bunch!
Hey guys, this worked for me as well. However, I'm pretty confused. Here is microsoft giving us a marvelous developement environment for free, but it's hell to distribute programs made by it. I make small programs and would like to run just the executable, without having to install something additional to allow it to run. Is there a possible fix for this? I appreciate any help, otherwise I'd be forced to look for a new compiler *sob*. Thanks guys.
Quote:
Original post by blankdev
I make small programs and would like to run just the executable, without having to install something additional to allow it to run.
Link to the static runtime library, and not the DLL one and this will solve your problem. I don't have VS2005 on this computer so I can't check where the actual setting is, but it's there somewhere :)
I'll have a look when I get to my laptop if anyone else hasn't answered in the meantime :)
Nevermind I got it, I think you mean multithreaded instead of multithreaded DLL? I hope not cuase then what about things like SDL that require multithreaded DLL lol, thanks bud. I'll keep looking.
EDIT: Yeah it seems to work. However my problem is when I have programs that need to have /MD (multithreaded dll) such as SDL. If anyone has a fix, I'd greatly, greatly appreciate it. Thanks bud for helping me out so far.
EDIT: Yeah it seems to work. However my problem is when I have programs that need to have /MD (multithreaded dll) such as SDL. If anyone has a fix, I'd greatly, greatly appreciate it. Thanks bud for helping me out so far.
Quote:
Original post by blankdev
Ah okay so I must do that with any library that needs that, okay then, thanks.
That works, yes. But it will obviously make your DLLs larger. The alternative is to use Microsofts new way of deployment (which is essentially a way to fight DLL hell). Eventually, everybody will have the appropriate runtime libs installed anyway.
Quote:
Original post by blankdev
What if it doesn't compile like that? For example I think FLTK requires /MD (multithreaded DLL).
I don't see why it wouldn't compile. The static and dynamically linked CRT libs are functionally equivalent.
Thanks Yann L.
What would this be? Would this be the installer I created thanks to the wonderful walkthrough by Nikola?
Quote:
The alternative is to use Microsofts new way of deployment (which is essentially a way to fight DLL hell). Eventually, everybody will have the appropriate runtime libs installed anyway.
What would this be? Would this be the installer I created thanks to the wonderful walkthrough by Nikola?
Quote:
What would this be? Would this be the installer I created thanks to the wonderful walkthrough by Nikola?
Yep, but there are a few more possibilities. Unfortunately, none of them is as easy as "just put everything into the executables directory". The advantage is that the new model avoids versioning conflicts (several CRT versions can coexist), and allow easy servicing, eg. for security patches in the runtime libs.
Read this for indepth information, and more specifically this.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement