transformer.net 2.1.1

Page 1 of 2 12 LastLast
  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)
    Vladimir Shcheglov
    Sr. Developer
  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 & CEO
  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 & CEO
  7. #7
    Thank you.
  8. #8

    Sorry to keep this open

    I had the same issue and editing the web.config was all that needed to be done. I just wanted to highlight that this may have been from nuget. When i started i had one binding redirect for asp.net MVC
    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
    Then i installed ext.net via nuget and got the following
    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
          <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" />
          <bindingRedirect oldVersion="1.0.0.0-4.5.9" newVersion="4.5.10" />
          <assemblyIdentity name="Ext.Net.Utilities" publicKeyToken="2c34ac34702a3c23" />
          <bindingRedirect oldVersion="0.0.0.0-2.0.1" newVersion="2.1.0" />
          <assemblyIdentity name="Transformer.NET" publicKeyToken="e274d618e7c603a7" />
          <bindingRedirect oldVersion="0.0.0.0-2.0.0" newVersion="2.1.0" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Transformer.NET" publicKeyToken="e274d618e7c603a7" culture="neutral" />
          <bindingRedirect oldVersion="0.0.0.0-2.1.1.22883" newVersion="2.1.1.22883" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
    I'm not 100% on how this config section is handled but from an xml point of view it doesn't seem logical or it would be difficult to handle this config section and try to figure out what redirect applies to which assembly. So after applying your fix I ended up with the following and i didn't get the exception.

    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
          <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
        </dependentAssembly>
        <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" culture="neutral" />
          <bindingRedirect oldVersion="0.0.0.0-2.1.1.22883" newVersion="2.1.1.22883" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
    So all i'm trying to highlight here is that when i install from nuget i got a funky looking config section that needed cleaning so i'm not sure if this helps narrow down what is happening.

    MB
  9. #9
    FWIW Using frostfang's

    <bindingRedirect oldVersion="0.0.0.0-2.1.1.22883" newVersion="2.1.1.22883" />
    line was the only way for me to get NuGet installed Ext.Net running for 2.1.1 due to the same exception as the original post.
  10. #10

    Thanks

    Thanks Justin and frostfang - worked for me too


    Quote Originally Posted by Justin Wignall View Post
    FWIW Using frostfang's

    <bindingRedirect oldVersion="0.0.0.0-2.1.1.22883" newVersion="2.1.1.22883" />
    line was the only way for me to get NuGet installed Ext.Net running for 2.1.1 due to the same exception as the original post.
Page 1 of 2 12 LastLast

Posting Permissions