MDX Reference Hell!!!

Why do the .Net DirectX components not adhere to the same programming interface across versions? Why should I have to have more than one version on my machine at once? I can''t compile old C# directX programs I''ve written without changing the DX references form version 1.0.1901.0 of MDX to the 1.0.900.0 libs. I don''t even understand why this should be the case. If I want to distribute my DX9 source code to anyone, they should be able to compile it without screwing around with the DX references. It seems like if this problem is not fixed soon (before more versions come out) there''s going to be an instance of "DLL Hell" for these references. I shudder to think of trying to get something to compile where the programmer has mixed versions for different components (DPlay, DSound, D3D, ect...) Or am I just missing something simple? If I uninstall the old references, will the code find the new ones automatically? ---------------------------------------- Let be be finale of seem, seems to me. ---------------------------------------- Coding: http://www.stanford.edu/~jjshed/coding Miscellany: http://www.stanford.edu/~jjshed