locked
DirectX required permissions RRS feed

  • Question

  • I'm helping to get a program written in C# .NET 1.1 to work online as an embedded object in a webpage.  The program uses DirectX and I have modified it to the point where it works when given FullTrust permissions.  However, since this is not the default, can anybody think of other ways to approach this?

    Basically I turned the main form into a UserControl, which uses DirectX to display everything.  When given FullTrust, the display works.  When not, as soon as the UserControl gets created, a SecurityException is thrown:

    System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

    Does anybody know exactly what permissions DirectX needs?  Or is there a different way to code the display using a technology that is common to IE, like Flash?
    Sunday, February 25, 2007 10:08 PM

Answers

  • Managed Direct requires FullTrust. This effectly means that running an MDX app in a web page is a non starter. Its just not a scenario the DirectX team considers a high priority. There is no way to work around this without creating a huge security problem on the computer and I can't recommend you even try to do this.

    The only MS technology for doing 3d in a browser is the WPF stuff.

    The otehr thing you could try is to build an ActiveX control - this way the security decision is handled by the end user who can choose to trust your application or not. However the responsibility is now all on you to ensure the code is fully safe and you also need to think about code signing dependign on your deployment

     

    Monday, February 26, 2007 7:37 PM