Reputation: 63728
It's a common problem where developer PCs have D3DX redists and VC++ redists installed, which end-user PCs may not. If you have a "clean PC" for installation testing, the moment you install then it's no longer clean.
Specifically for D3DX redists, is there a way to remove the redists so my app won't work unless it's installer properly installs required redist versions?
Upvotes: 2
Views: 169
Reputation: 41067
D3DX is not a 'windows protected file' DLL, so you can just delete it with administrator rights on a test system.
This advice comes with three caveats:
Ideally new apps should even be using D3DX anymore. See Living without D3DX.
If you do need to use legacy components like D3DX, be sure to read Not So Direct Setup so you understand exactly what DXSETUP does and doesn't do, and you read the instructions on trimming down the CABs to just those that you need.
If you are using DXSETUP, be sure to use the refreshed version and not the one that came inside the DirectX SDK (June 2010). This resolves some issues with systems that only have .NET 4.x and do not have .NET 2.0/3.x installed.
Upvotes: 1
Reputation: 64845
Virtual machines. Many VMs also have a feature to create a save point of the virtual harddisk so you can quickly rollback any changes to the disk since the save point was made.
Upvotes: 5