+1-888-365-2779
Try Now
More in this section

Forums / Deployment / Nolics on Production Server

Nolics on Production Server

3 posts, 0 answered
  1. GCM
    GCM avatar
    11 posts
    Registered:
    29 Jul 2007
    17 Sep 2007
    Link to this post
    I having a working Sitefinity site on my development server, but when I uploaded to the production server I receive the error message below.  This error occurs for any page on the site.  I'm sure we copied all the project files and I even check to see if teh Nolics.Engine.v4.2.dll was in the bin folder on the production server.  Thanks.

    Joel

    Could not load file or assembly 'Nolics.Engine.v4.2, Version=4.2.2520.4, Culture=neutral, PublicKeyToken=c50af72fde0670b7' or one of its dependencies. The module was expected to contain an assembly manifest.
  2. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Sep 2007
    Link to this post
    Hi Joel,

    Sitefinity 3.0 SP2 is built with Nolics version 4.2.2520.4.
    Please make sure that Nolics.Engine.v4.2.dll assembly version number is 4.2.2520.4.

    However, you could also use a different Nolics version. In this case, you should declare Binding Redirect in the web.config, e.g:
    <runtime> 
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">  
            <dependentAssembly> 
                <assemblyIdentity name="Nolics.Engine.v4.2" publicKeyToken="c50af72fde0670b7" culture="neutral"/>  
                <bindingRedirect oldVersion="4.2.2520.4" newVersion="4.2.2522.4"/>  
            </dependentAssembly> 
        </assemblyBinding> 
    </runtime> 
     
     

    Hope this is helpful. Please let us know how it goes.

    Regards,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  3. GCM
    GCM avatar
    11 posts
    Registered:
    29 Jul 2007
    17 Sep 2007
    Link to this post
    I did a little more research on that error message and it just seems like the file was corrupt.  The BadImageFormatException was being thrown.  I deleted the file and the uploaded it again.  Works fine now. Thanks.

    Joel
Register for webinar
3 posts, 0 answered