Upgrading v1.93 to v1.94

From
Revision as of 08:48, 23 February 2020 by Thewikiadmin (talk | contribs) (Created page with " = Upgrading v1.9.3 to v1.9.4 =   #Make a backup of the existing installation, especially the web.config file. #You can maintain the existing IIS application and confi...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Upgrading v1.9.3 to v1.9.4

 

  1. Make a backup of the existing installation, especially the web.config file.
  2. You can maintain the existing IIS application and configuration; no changes in .NET framework or any other IIS configuration needs to be altered.
  3. The upgrade package includes the following:
2020-02-18  04:39 PM    <DIR>          bin
2020-02-18  04:39 PM    <DIR>          Content
2020-02-18  04:39 PM    <DIR>          CSS
2020-02-18  04:39 PM    <DIR>          Images
2020-02-18  04:39 PM    <DIR>          Views
2019-07-30  03:47 PM               495 ContextMode4.aspx
2019-01-13  08:02 PM             1,279 ContextMode5.aspx
2018-02-24  02:04 PM            32,038 favicon.ico
2019-01-13  08:02 PM             1,717 FormLogin.aspx
2019-01-13  08:02 PM             1,704 FormLogout.aspx
2019-01-13  08:02 PM             1,253 generate_license.txt
2018-01-09  07:17 AM               868 LICENSE.txt
2019-01-13  08:02 PM               119 metadata.aspx
2020-02-17  03:05 PM             1,601 packages.config
2020-02-18  04:39 PM                49 PrecompiledApp.config
2019-01-13  08:02 PM             1,778 upgrade.txt

 

  1. You should delete the corresponding folders and files in the current installation.  It is recommended that a delete is performed first instead of an overwrite.  This is due the dependencies that may exist with the DLL files in the /bin folder.  Keeping old versions of DLLs may cause version conflicts.
  2. Make sure you do not remove the following:
  •     /certificates folder (or alternate location)
  •     /logs folder (or alternate location)
  •     /start folder
  •     /app_data folder (if exists)
  •     /web.config file
  1. Stop the IIS site temporarily as there may be file locks in place.
  2. Wait a few seconds.
  3. Copy the contents of the ZIP package into the folder where STS was located.
  4. Update the web.config with the following elements:
    1. Update the version:
    
     <STSSettings Version="v1.93" ...
     change to:
     <STSSettings Version="v1.94" ...
  1.    Add the new parameters "ClearSession" and "PrimaryADGroupCheck""
     <STSSettings Version="v1.93" ConfigurationDatabase="~/App_Data/Orbital.sqlite" ...
     update to:
     <STSSettings Version="v1.94" ConfigurationDatabase="~/App_Data/Orbital.sqlite" ClearSession="false" PrimaryADGroupCheck="false" ...
  1.     Add the new parameter "TokenTimeSpan" in each SAMLConfiguration element:
  
      <SAMLConfigurationElement Service="MyService" AssertingParty="sts.hospital.org" ...
      update each SAMLConfigurationElement to:
      <SAMLConfigurationElement Service="MyService" AssertingParty="sts.hospital.org" TokenTimeSpan="2" ...
  1.       Update the entire Runtime section:
        <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Optimization" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="1.1.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="2.0.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="WebGrease" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-1.5.2.14234" newVersion="1.5.2.14234"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

  replace with the following: 

   <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <dependentAssembly>
                <assemblyIdentity name="Antlr3.Runtime" publicKeyToken="EB42632606E9261F" culture="neutral"/>
                <bindingRedirect oldVersion="0.0.0.0-3.5.0.2" newVersion="3.5.0.2"/>
            </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Optimization" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="1.1.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="WebGrease" publicKeyToken="31bf3856ad364e35" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-1.5.2.14234" newVersion="1.5.2.14234"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Helpers" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.WebPages" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35"/>
        <bindingRedirect oldVersion="1.0.0.0-5.2.7.0" newVersion="5.2.7.0"/>
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System" publicKeyToken="b77a5c561934e089" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

 

  1. Start the IIS site
  2. Launch the web application to test and verify that the log files display no errors.

 

 

Retrieved from "https://sts.radiusworks.com/wiki/index.php?title=Upgrading_v1.93_to_v1.94&oldid=56"