 |
We don't currently load assemblies, it should be done by the user. Sorry for the inconvenience. But maybe we can investigate what you suggested: looking for the xmlns assembly definition and try to load it ourselves. |
 |
Ah that explains it :-) Maybe even better and easier for you, just provide a callback for resolving these DLLs (these could be either native or managed)? |
|
|
Yes, that sounds event better. It could be valid for native libraries too, you are right. |
|
|
By the way, we just generated a new beta for the C# SDK you can download here: https://drive.google.com/open?id=0Bwl3Ci5GLsE8dms4RkhWcFBzems Please create new tickets for the issues you find. We appreciate your feedback. |
 |
There are a few important changes regarding textures in this new version: 1. WrapTexture methods are no longer part of the TextureSource. The Texture source is now built using a Texture (same as C++ API) 2. We expose separate WrapTexture methods to create a Texture using a ID3D11Texture2D (sorry for this breaking change) 3. Texture has a object field to optionally hold the object with the ownership of the native handle 4. There will be also a callback clients must set to load textures from URI. You are in charge of creating the textures now. |
- Anonymous
