No Managed DirectX for 64bit?

No Managed DirectX for 64bit?

• kasakaimumbai

  I downloaded the latest DirectX SDK, Oct 2005.
  
  Still NO Managed DirectX for 64 bit.
  
  

• causal

  @JLucak: see this workaround ... maybe it helps in the meantime ...
  
  
  

• LucasC

  I am trying to use other approach... Just need to compile my program in Win64 for x86 intead of x64 ... the problem is how to make my .NET exe x86 and not x64 using the vc# express IDE ( with the command line I could do /platform:x86, but i dont see this option in the IDE ) Pls tell me if you have other ideas... I can't get the MDX9 libraries to run ok in win64 and i am desperated.
  
  

• beN!

  Hi John,
  
  I havent heard any info about it as well. I have emailed irectx@microsoft.com" href="mailtoirectx@microsoft.com">directx@microsoft.com for additional information. Will post it as soon as I heard some information from them.
  
  Regards,
  Vikram
  
  

• NimoTh

  Here is the reply I received from DirectX Team @ Microsoft:
  ------------------------------------------------------------------
  The DirectX Team is currently in the planning phase and do not have
  specific time-lines.  But our goal is to have 64-bit version the ships
  at the same time as Whidbey or shortly there after.
  
  Thanks,
  DirectX
  ------------------------------------------------------------------
  
  Regards,
  Vikram
  
  
  
  

• AZ-xyz

  DirectX x64 Samples are available for C++ so I assume that DirectX is x64 ready.

  Will there be a .NET x64 version of DirectX besides WPF

  
  
  

• Ricky Wen - Microsoft

  DirectX x64 Samples are available for C++ so I assume that DirectX is x64 ready.

  Will there be a .NET x64 version of DirectX especially a DirectSound implementation

  
  
  

• TOWFAS

  @JLucak: that's correct. It's a 32-bit workaround to work and test DX apps until 64-bit version is released.
  
  
  

• walking fish

  Thanks, but unfortunately this does not help. The suggestion essentially turns my app back into a x86 executable, which means that the limitations on the address space are back down to 2GB. The whole reason for pursuing the 64 bit application was to gain access to a larger address space. Until the Managed DirectX is released that links to the 64 bit version of DirectX, it seems that I am out of luck.
  
  - JLucak
  
  

• PetroWEB

  Sigh...

  I'm Still getting the BadImageFormatException with DX SQK Feb 2007... under Vista 64....

  Here we go for the "/platform:x86" workaround...again

  Are ya kidding

  
  

• Thore

  I downloaded the recent August 2005 DirectX9 SDK ... Also the Visual C#
  Express Beta 2 and a Windows XP Professional 64 Bits Trial ... I tryed to
  compile a very simple example and got this exception when I try to executed
  the successfully-compiled example:
  
  System.BadImageFormatException was unhandled
    Message=" is not a valid Win32 application. (Exception from HRESULT:
  0x800700C1)"
    Source="WindowsApplication1"
    StackTrace:
        at WindowsApplication1.Form1.button1_Click(Object sender, EventArgs e)
  
        at System.Windows.Forms.Control.OnClick(EventArgs e)
  
        at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
  
        at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
  button, Int32 clicks)
  
        at System.Windows.Forms.Control.WndProc(Message& m)
  
        at System.Windows.Forms.ButtonBase.WndProc(Message& m)
  
        at System.Windows.Forms.Button.WndProc(Message& m)
  
        at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
  
        at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
  Int32 msg, IntPtr wparam, IntPtr lparam)
  
        at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
  
        at
  System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32
  dwComponentID, Int32 reason, Int32 pvLoopData)
  
        at
  System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
  reason, ApplicationContext context)
  
        at
  System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason,
  ApplicationContext context)
  
        at WindowsApplication1.Program.Main() in
  c:\WindowsApplication1\WindowsApplication1\Program.cs:line 16
  
        at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
  
        at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
  
        at System.Threading.ExecutionContext.Run(ExecutionContext
  executionContext, ContextCallback callback, Object state)
  
        at System.Threading.ThreadHelper.ThreadStart()
  
  
  My code is pretty simple and compiles OK....
  
  using System;
  using System.Windows.Forms;
  
  using Microsoft.DirectX;
  using Microsoft.DirectX.Direct3D;
  
  namespace WindowsApplication1
  {
      public partial class Form1 : Form
      {
          public Form1()
          {
              InitializeComponent();
          }
  
          private void button1_Click(object sender, EventArgs e)
          {
              Vector3 l_v1 = new Vector3(1, 2, 3);
              Vector3 l_v2 = new Vector3(4, 5, 6);
              float l_flDot = Vector3.Dot(l_v1, l_v2);
  
          }
      }
  }
  
  The problem I think is that the Managed DirectX has been compiled using .NET
  1.1 for ONLY x86 architecture ( I saw it with ILASM ) ... Must be this
  because with x86 version of Windows XP Pro my example works ok....
  
  So no... August 2005 SDK ( released YESTERDAY ) dont support Win64... Hope they port it to x64 soon.....
  
  
• No Managed DirectX for 64bit?