transformer.net 2.1.1

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    transformer.net 2.1.1

    Hi

    I'm getting this exception error with transformer 2.1.1

    Could not load file or assembly 'Transformer.NET, Version=2.1.0.0, Culture=neutral, PublicKeyToken=e274d618e7c603a7' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    If I backtrack to 2.1.0 the exception isn't thrown.

    Is there a dodgy reference in there?
    Or have I simply got something wrong?

    Chris
    Last edited by geoffrey.mcgill; Dec 17, 2012 at 1:19 PM. Reason: please use [CODE] tags
  2. #2
    Did you rebuild Ext.Net with new Transforner.NET?
    Ext.Net version from Nuget still uses Transformer.NET 2.1.0

    Difference between 2.1.0 and 2.1.1 versions of Transformer.NET that 2.1.1 can be used with Medium trust level (2.1.0 with Full only)
  3. #3
    Quote Originally Posted by Vladimir View Post
    Did you rebuild Ext.Net with new Transforner.NET?
    Ext.Net version from Nuget still uses Transformer.NET 2.1.0

    Difference between 2.1.0 and 2.1.1 versions of Transformer.NET that 2.1.1 can be used with Medium trust level (2.1.0 with Full only)
    Ye we did rebuild, and we got the 2.1.1 via Nuget.
    A colleague has just got Transformer.NET 2.1.1 working, after 'editing' the web.config file

    Chris
  4. #4
    Quote Originally Posted by ChrisO View Post
    Ye we did rebuild, and we got the 2.1.1 via Nuget.
    A colleague has just got Transformer.NET 2.1.1 working, after 'editing' the web.config file

    Chris
    I have updated the Web.config files in SVN with the new <assemblyBinding> information. The following should work with the Ext.NET 2.1.1 release.

    Example

    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
          <bindingRedirect oldVersion="1.0.0.0-4.5.9" newVersion="4.5.10" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Ext.Net.Utilities" publicKeyToken="2c34ac34702a3c23" />
          <bindingRedirect oldVersion="0.0.0.0-2.0.1" newVersion="2.1.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Transformer.NET" publicKeyToken="e274d618e7c603a7" />
          <bindingRedirect oldVersion="0.0.0.0-2.1.0" newVersion="2.1.1" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
    Hope this helps.
    Geoffrey McGill
    Founder
  5. #5
    Is this something that will be 'rectified' in the next release.

    Are there any issues with us sticking with transformer.Net 2.1.0 until the next release?
  6. #6
    As posted by Vladimir above:

    Difference between 2.1.0 and 2.1.1 versions of Transformer.NET that 2.1.1 can be used with Medium trust level (2.1.0 with Full only)
    There's no issue with Transformer.NET, unless you are attempting to use in a Medium Trust environment.
    Geoffrey McGill
    Founder

Posting Permissions