exe of the application that needs it (or modify the appropriate environment variable) dll into your system32 folder and it still doesn't see it, you might instead need to put it into the same folder as the. And the fact that this issue is so obscure to both developers and users is a ramification of a design decision made on Microsoft side.Īlso, if you put this. But I agree they could still provide a generic version for download anyways, so that the users who happen to not have this file could still get it without resorting to suspicious third-parties. dll their application relies on, and Microsoft is not obliged to provide it. So technically it's the fault of the people who fail to ship the. Furthermore, you need to know how to build it (or rather, know where to look to know how to build it - (VS.71).aspx) dll instead of having its code incorporated into it internally). But it's so common that many products are shipped without it, often because developers aren't even aware that they're supposed to ship it - they have it on their system and never get any problem. The thing is, msvcp71.dll is not a part of any framework, but rather it's supposed to be built and shipped along with the application that is designed to rely on this external.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |