directx path problem?

Was it compiled using the (SDK only) debug libraries?

Libs are:

d3d9.lib - stub library for Direct 3D, link is with d3d9.dll at runtime, debug level controlled by Control Panel
d3dx9.lib - the release library for D3DX, full code no dll
d3dx9d.lib - the stub library for D3DX, link is with the (SDK only) d3dx9d.dll at run time
d3dx9dt.lib - debug library for D3DX, full code no dll - useful if giving to someone without SDK installed for testing.

Is the device being created using the Reference Rasterizer? It's only available on a system with the SDK installed.

Your app really shouldn't be crashing if you handle failures gracefully. You should also read the Forum FAQ about debugging DX apps.

I get the feeling im missing something...

When i'm in Visual Studio. I add reference to various DirectX files from "C:\WINDOWS\Microsoft.NET\Managed DirectX\v9.03.91" (This folder is only created when the SDK is installed). I just browse the list of .NET references.

I Don't "Copy Local" these dll's as i figured it should be using the ones already installed by the users' directx run-time.

Should I be pointing my references to a different set of dll's?

I think i found the problem.

When installing DirectX 9.0c runtime there is a seperate install for Managed DirectX... As a C# programmer, i find this very annoying. Should be all installed at once.