9/11/2023 0 Comments Directx end runtime![]() This self-sufficient program is useful if you're using applications that have heavy multimedia elements. But problem appears when I install the same package on the second 64-bit box: for some reasons prerequisite condition doesn't work properly there - it tries to find D3DCompiler_43.dll and D3DX9_43.dll not in C:Windows\System32 but in C:Windows\SysWOW64 folder.Ĭan someone explain why it looks in SysWOW64 even if I hardcode path to C:\Windows\System32?Īnd one more question - probably someone knows a better way how to check if DirectX End-User-Runtime is installed on target box? I found similar topic here check registry for DirectX End-User Runtime, but I cannot understand how and where in Prerequisite Editor can I use LoadLibrary("d3dx9_43.dll") function.DirectX End-User Runtime Web Installer Editor's Review DirectX Prerequisite condition works fine on the first box - it installs DirectX only if both D3DCompiler_43.dll and D3DX9_43.dll are missed in C:\Windows\System32. I tested my installation package on two 64-bit Win7 boxes. ![]() Install DirectX End-User-Runtime if files ![]() So, I'm adding conditions for my prerequisite: My product is a 64-bit application and it requires some directX files in C:\Windows\System32 folder (At least I know that it won't work without D3DCompiler_43.dll and D3DX9_43.dll). I don't want install DirectX End-User-Runtime every time I install my product, so I want to add a condition for DirectX in Prerequisite Editor. ![]() Product requires DirectX End-User-Runtime to be installed, so I created custom prerequisite for DirectX in my InstallShield solution. I'm using InstallShield 2013 (Basic MSI Project) to create installation package for my product. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |