Printable View
Hi,
I have searched the web and read the msdn tutorial but I can't find anywhere the answer to this anywhere:
I used the deployment project in MSVS .NET 2003 to install my application but I would like to detect if the computer has DirectX >= 9.0 and I can't figure out how to do it and if it's even possible. Any help would be greatly appreciated. Thanks
Amish
It's possible. So a search for "getdxver" (i think that's the name). I believe it comes with the SDK, and shows you how to check for versions.
Thanks for the answer. This is a C++ function call. I don't think I can use it in a deployment project.Quote:
Originally Posted by TheColonial
Amish
why not? :)
FYI, It's definitely possible.
Could you explain how to do it or point me to someplace that has more information on the subject. ThanksQuote:
Originally Posted by TheColonial
Amish
You could just include the directx 9 installer in your installer (Microsoft licensing allows you to do this) then it will ask the user if we wants to install directx 9 and update his componants as necercary.
But I need the installer to check for previous version of directX first and then if the version is less than 9.0 install it
Amish
Check for "Launch Conditions Editor", it will allow you to check what files are on the users machine. Additionally it can check the versions of that file, as well as alot of other nifty things.
Also check out "Custom Actions", It allows you to check the status of a flag, these flags can be set by "Launch Conditions". So if you check that a file of a certain exists, and lets say it does exist so it sets that flag. When your installer runs it will check that flag, if it's set to false it will launch your DirectX installer for instance, if it's true it won't launch your DirectX installer.
I still dont' get how you can write code in the distribution project though, maybe TheColonial can shed some more light on this since I can't seem to find such a thing..except for time consuming hacks using piping and editing the setup file via asm.
I think your other options would be:
1) Include the DirectX Installer with your Installer
2) Make your own installer file, that way you have all the options you want
3) Check what DX version the user has when the user executes your program, when it can't find DirectX it will ask the user to run a seperate installer (of course you can put this on your distribution disc or on the users computer, maybe if you're distributing it via internet win-zip self extractors might not be out of question).