Good. For once, my notorious verbosity has served its intended purpose.nyogtha993 wrote:Well, you were much more helpful than any of the websites I was going to before!
Yes, in theory, it should work. That is the "official" way you're supposed to do it - "the gospel according to Microsoft", so to speak.nyogtha993 wrote:Anyway, I used the DLL deployment method found at the bottom of the page you linked me. Everything's in there now, so do you think it should work? I might as well know before I start posting more links.
Mind you, I did try to install those files manually myself and it didn't actually work. But this could just be because the "assembly / manifest" stuff in your program didn't match up with what I was doing, rather than that this way of doing things won't work.
But, well, I'm afraid the only way to know that for certain is to just try it. It should work because that's the way Microsoft want you to "officially" do it. At least, if it doesn't work, then it becomes Microsoft's fault why it isn't working and not yours.
Static linking, though, would definitely solve it.
As it simply bundles everything the program needs inside the EXE itself, so that it's completely stand-alone and has no external dependencies at all. Nothing can be found to be missing, because you're sticking the whole damn lot inside the EXE itself. It's not as graceful, perhaps, but it's guaranteed to work. It's basically the "brute force" method for this kind of problem.
As you might have guessed from the fact that I don't have those MSVC DLLs sitting on my system already, I tend not to use Microsoft's tools. So how easy or hard it might be to change the linking options with what you've got there, I don't know.
It's fairly easy with the tools I have but then, well, there was a reason why I don't use Microsoft's tools, when I can help it, because they do have this uncanny ability to turn even the most simple things into complicated nightmares. Ah, I long for the day when a *NIX finally takes over from Windows and we can all concentrate on actually programming and not pissing about nannying tools and making up for Microsoft's faults all day long. But that's another thread for another day.









