version upgrades

Posted by: dan-fp on 8 September 2017, 12:47 pm EST

  • Posted 8 September 2017, 12:47 pm EST

    I just installed the aug builds of Spread 3 for Windows Forms; I was using the beta builds.  The license expired (obviously).  I ran the app with the new version installed but the app fails because of the license error. 

    In my builds i have "copy local" = false and "Specific Version" = false.  i was thinking this would let me replace the dlls with the newer versions and no recompile would be necessary.

    I removed all but the Aug. builds from the GAC and the app is still looking for the 2001 (beta) builds.

    Is this the way it is supposed to work?  I hope that i won't have to recompile all the projects with every version change.
  • Replied 8 September 2017, 12:47 pm EST

    Did you update your project references to use the new version?
  • Replied 8 September 2017, 12:47 pm EST

    <span>************** Exception Text **************
    System.IO.FileLoadException: Could not load file or assembly 'FarPoint.Win.Spread, Version=3.0.2001.2005, Culture=neutral, PublicKeyToken=327c3516b1b18457' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
    File name: 'FarPoint.Win.Spread, Version=3.0.2001.2005, Culture=neutral, PublicKeyToken=327c3516b1b18457'

    My projects show i compiled against 3.0.2004.2005.  I recompiled and get this error.

    I don't want to have to recompile at all.
  • Replied 8 September 2017, 12:47 pm EST

    Yes, I eventually found the problem.  Even though the references showed the correct version number that wasn't enough.  There is a file located in the Properties (C#) (My Project (VB)) directory named licenses.licx.  It has this line:

    FarPoint.Win.Spread.FpSpread, FarPoint.Win.Spread, Version=3.0.2001.2005, Culture=neutral, PublicKeyToken=327c3516b1b18457

    I had to change the 2001 to 2004 then the recompile worked.

    FarPoint.Win.Spread.FpSpread, FarPoint.Win.Spread, Version=3.0.2004.2005, Culture=neutral, PublicKeyToken=327c3516b1b18457

    Certainly that isn't required for every upgrade.

  • Replied 8 September 2017, 12:47 pm EST

    Normally the upgrade steps in the readme should work.
  • Replied 8 September 2017, 12:47 pm EST

    So why don't they work in this case?  What is the licenses.licx file?  Why does it have the full name of the Spread?  How come when i delete that file an the reference to it from the project file does it get recreated?
  • Replied 8 September 2017, 12:47 pm EST

    The license file is created by Visual Studio so it will get recreated when you delete it and reopen the project.  What exact steps did you use to upgrade the project?  Did you have any forms or code windows open while upgrading?
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels