Managed DirectX Bootstrapper package

Today I release a Managed DirectX Bootstrapper package on GotDotNet.  (You can also find a previously released Bootstrapper package for deploying the 1.1 Framework as well.)

You can check it out here:

This will allow you to ClickOnce deploy applications which use Managed DirectX and use the Bootstrapper to detect / install Managed DirectX if it isn't on the target machine.


Comments (4)

Cancel reply

  1. Iain says:

    I want to inlcude managed DX in my installer and was VERY pleased when I came across this.

    Of course, there’s a but coming on. It doesn’t work…!

    I’ve tried it with the June and October versions and both times the setup project fails to build. The main problem appears to be that teh file names are changed. E.g. your package is expecting ‘ManagedDX.CAB’ and the equivalent is now (probably)’’.

    Also I would guess that check needs to be changed to llok for the current version (June, Oct …) in the GAC, but I’m not too clear on how to do this (frankly, I’ve avoided installers like the plague after an abortive attempt to get to grips with the Windows Installer docs 5 or so years ago!).

    Can you help?


  2. Iain says:

    What I did was to change all the names in the manifest to those of the files in the redist package.

    And also remove the command that includes the manaed cab (because it has now dissapeared).

    This allowed me to build the installer (with the DX9 stuff as a prerequisite). Unfortunately, although it runs and seems to install (and forces a reboot), it does NOT install the managed bits (the machien already had 90c on so I don’t know if it did anything at all!)

  3. If you need to change the version that it checks for, open product.xml, go to the section marked <InstallChecks> and modify the "Version" and "PublicKeyToken" for FoundMDXAssemblies to reflect the correct version. You can get these values from the aseembly directory in the GAC.

Skip to main content