Web file manager Free Installation assistance Manual Home page

Update notes

For general update instructions see How can I update my existing installation with latest version without losing config and settings?. This page contains notes about new functions you have to configure, compatibility breaking changes, security issues and other information you should be aware of in upgrading process.

Update to version 5.0.3

Starting from version 5.0.3, a new parameter PublicLinkUrlPathName has been added to indicate a friendly relative path for public links. After upgrading to version 5.0.3, be sure to configure anonymous access for this path.

For update to version 5.0.3 from 5.0.2, 5.0.1 and 5.0.0

In the runtime section of the Web.config file, update the version of libraries Newtonsoft.Json to 12.0.0.0, Microsoft.IdentityModel.Tokens, System.IdentityModel.Tokens.Jwt to 5.4.0.0, BouncyCastle.Crypto to 1.8.4.0, RestSharp to 106.4.2.0, and add new assemblies Microsoft.IdentityModel.Protocols, Microsoft.IdentityModel.Protocols.OpenIdConnect:
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
            <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Tokens" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.4.0.0" newVersion="5.4.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="System.IdentityModel.Tokens.Jwt" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.4.0.0" newVersion="5.4.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Protocols" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.4.0.0" newVersion="5.4.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="Microsoft.IdentityModel.Protocols.OpenIdConnect" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-5.4.0.0" newVersion="5.4.0.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="BouncyCastle.Crypto" publicKeyToken="0e99375e54769942" culture="neutral"/>
            <bindingRedirect oldVersion="0.0.0.0-1.8.4.0" newVersion="1.8.4.0" />
        </dependentAssembly>
        <dependentAssembly>
            <assemblyIdentity name="RestSharp" publicKeyToken="598062e77f915f75" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-106.4.2.0" newVersion="106.4.2.0" />
        </dependentAssembly>
    </assemblyBinding>
    <AppContextSwitchOverrides value="Switch.System.IO.UseLegacyPathHandling=false;Switch.System.IO.BlockLongPaths=false" />
</runtime>
To go to 5.0.3 from 4.x, see below, except section assemblyBinding (for update assemblyBinding section see above).

Update to version 5 from 4.6 and below

NOTE! Automatic updating to version 5 (and higher) from the Admin Panel is possible only with version 4.6.6. From previous versions, after the update, the application starts with an error, is this case use Manual upgrade.

Dropped support for .Net Framework 4.0. Now application requires .Net Framework 4.7.2 or above.
Install latest version of .NET Framework (see .NET Framework installation).

Changes in Web.config file



Update to version 4.5 from 4.0 and below

Changes in the data storage method

Starting from the version 4.5 we implemented support of SQLite database and most of the data from XML files are moved into DB. Now the list of anonymous links (Links.xml), event log (Log.xml), watching the users, list of recents, favorites are stored in an SQLite database file (Data\data.db). After the upgrades procedure, the first time you run the application data are imported from XML files into the database. This procedure is absolutely automated and you should not do anything unless error occured .
In case you can't find your old data after upgrade, please check error details in Error Log at Admin Panel and contact support (do not forget to attach output of diagnostics.aspx page)
Attention! Before upgrade, make sure that you have made a backup copy of the XML files from Data folder.

Changes in HttpCommanderSettings.config

All settings related to the public links functionality are moved to a new section PublicLinks (from Main and UI sections).
Attention! Before you upgrade, make sure that you have made a backup copy of the file HttpCommanderSettings.config.
In case you can't find your old settings related to Public Links after upgrade, please check error details in Data\debug.log file and send it to support team.

Added Windows Search Service support

Starting from version 4.5, HTTP Commander support the search using the Windows Search Service (parameter SearchMethodOfFiles). It allow to perform full-text search in files and significantly increase search speed in compare to the build-into HTTP Commander a search method. In order to activate support of Windows Search you need to install and configure Windows Search Service and to add all shared folders to the list of indexed locations. See Windows Search Help for more details.

Dropped support for OAuth v1 authentication and API v1 for Dropbox

If you have configured integration with Dropbox (EnableDownloadToDropbox, EnableUploadFromDropbox), and used OAuth v1 authentication, and the value of the DropboxConsumerKey setting is set to default (Element-IT key), then you need to get your own key and specify the value obtained. To do this, refer to the Integration with Dropbox instructions.

Update from 2.0.5 and below

If you are upgrading from version 2.0.5 (or below) to version 4.5+, in the file HttpCommanderSettings.config replace <UploadEmailNotification> on <EmailNotification> and </UploadEmailNotification> on </EmailNotification>.


Updated from 3.1.9 and below



Update from 2.0.11 and below

Format of public links changed from version 2.0 .
After upgrade from version 2.x to any newer version, existing public links may not work.
The easiest way to make them work again is to:

  1. Stop application pool
  2. open /Data/Links.xml file in text editor
  3. Search for <createdfor>GoogleView</createdfor> and replace with <createdfor>Share </createdfor>
  4. Save Links.xml, start app pool and check list of public links.

Changed the settings to support WebDAV

If you are used to access folders via WebDAV necessarily refer to Web folders mapping to properly configure.
If You enabled parameter AnonymousEditingOffice, the path to connect WebDAV folder begins with http://yourdomain/HTCOMNET/hcwebdav/0/ (suffixed '0').

New SVG icons

If you used IIS7+, add to Web.config file in <system.webServer> following static content section:

<staticContent>
    <remove fileExtension=".svg" />
    <mimeMap fileExtension=".svg" mimeType="image/svg+xml" />
</staticContent>

Changed authentication type with Google Drive, Dropbox, OneDrive to OAuth 2.0.

For more info see article Integration with Clouds Storages.


Update from 2.0.5 and below

Dropped support for .Net Framework 3.5. Now application requires .Net Framework 4.0 or above.

Email notifications. In HttpCommanderSettings.config file rename UploadEmailNotification section to EmailNotification. See Email notifications settings.


Update from 2.0.3 and below

New version slightly changes configuration file format breaking compatibility with older versions. Configuration files from earlier versions of application load to new version without problem, but updated files will not work correctly in legacy HTTP Commander.

Relax NTFS permissions to Data folder. Earlier versions required a number of accounts to have modify permissions to files of Data folder. Now only application pool identity requires modify access. See NTFS permissions for more details.


Update from 2.0.0.2012.11.06 and below

Enhanced "Force Logout" function — force the browser to forget user credentials of the current user at logout. See How to clear windows authentication on Log out to configure this option. If not configured, web browser will show logon dialog after logout. It is safe to ignore this prompt, however this behavior may be confusing.