Home » Discussion forums » OpenTK » Development
hack2root's picture

Fighting TypeLoaderExceptions - need Open Architecture Design imrovements for OpenTK assembly crossplatform loader

Posted Friday, 16 April, 2010 - 06:12 by hack2root in

I prefer fighting "exceptions" as "architecture design" features,

as well as well known TypeLoaderException exceptions by creating and supporting "confguration" files for different operating systems

I can advice merging my assembly configuration loader, which i wrote and have modified special version for OpenTK project

I brunched from my project here:

http://plugins.codeplex.com

I had use it by myself as replacement for .NET fw 4.0 for parallel extensions, managed extesibility framework, appication domain-safe type system.

Is it really a good news or a bad news for the community?

Who can support my activity to include best parts from my project to OpenTK?

‹ Matrix inversion function correctness issue spam ›

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
the Fiddler's picture

Re: Fighting TypeLoaderExceptions - need Open Architecture ...

Posted Friday, 16 April, 2010 - 07:46 by the Fiddler

From the project description, it sounds like a plugin system that comes with a number of useful plugins out of the box - is that correct? Can you describe in some more detail how this would work in the context of OpenTK? What are the advantages? Does it work on Mono and .Net 2.0 (which are the targets of OpenTK)?

The TypeLoaderExceptions were caused by the new security architecture in .Net 4.0. I have committed a workaround to SVN (https://opentk.svn.sourceforge.net/svnroot/opentk/branches/1.0), so if you are using that you can simply recompile for 4.0 after adding "NET40" to the project #define directives (project options -> Build).

hack2root's picture

Re: Fighting TypeLoaderExceptions - need Open Architecture ...

Posted Saturday, 17 April, 2010 - 03:05 by hack2root

First of all,

Thanks for the reply ;)

So, I imagined lightweight (by context, light means smallest as possible but not smaller binaries) subsystem driven by xml configuration files...

OpenTK is a loosely coupled, versioned component subsystem, embeddable, driven by configuration files. It adopts to almost any environments any opertaion system...

OpenTK.config

<xml ... />
<openTK>
   <core subsystem="windows">
      <extensions>
         <extension>
            <opengl version="1.0" path="~\home\mono\opentk\opencl.dll">
         </extension>
      </extensions>
   ...
   </core>
   <core subsystem="x11-mono">
      <extensions>
         <extension>
            <opencl version="1.0" path="~\home\mono\opentk\opencl.dll">
            <opengl version="3.0" path="~\home\mono\opentk\opengl30.dll">
            <opengl version="4.0b" path="~\home\mono\opentk\opengl40b.dll">
            <opengles version="1.0" path="~\home\mono\opentk\opengl1es.dll">
         </extension>
      </extensions>
   ...
   </core>
   ...
</openTK>
 

Benefits:
-availability to deploy application as cross-platform,
-availablility to change application OpenTK version on-the-fly

I need help to install mono on Windows 7 to port and test my sources on mono/linux.