| Age | Commit message (Collapse) | Author |
|---|
|
This is a defensive measure in case legacy path handling has been
enabled at the system level. Duplicati requires that legacy path
handling be _disabled_ to function properly.
Issue #4295 appears to be a result of legacy path handling being
enabled globally.
|
|
This updates all projects to target .NET Framework 4.7.1. The
TencentCOS and Tardigrade backends depend on .NET Standard 2.0. When a
.NET Framework prior to 4.7.1 is targeted, the system cannot be sure
that all the dependencies exist, so it copies all dependent assemblies
to the output directory. This causes many assemblies from the System
namespace to become bundled in the release.
https://stackoverflow.com/a/48875007
We had previously attempted to make individual projects target 4.7.1
(see pull request #4242), but this can cause compatibility issues when
4.6.2 projects depend on 4.7.1. projects.
This will require Mono 5.10.0 or greater (previously, we required 5.0.0
or greater).
https://www.mono-project.com/docs/about-mono/releases/5.10.0/#class-libraries
This fixes issue #4234.
|
|
`0.0.0.0-12.0.2.0` to `12.0.2.0`."
This reverts commit 93ace63d4f0cec18eb9b88c5f3d4ae024e8787fc.
|
|
`0.0.0.0-12.0.2.0` to `12.0.2.0`.
|
|
A known bug causes the incorrect config entry for system.net.http where we must be adjusted to 4.2.0.0
This bug gets fixed in .NET 4.7.2
|
|
resolves build warning for mismatching assemblies
|
|
|
|
and important to keep the aws sdk current
|
|
- no code changes except those noted below
- projects upgrade to 4.6.2
- wixinstaller project upgraded automatically by VisualStudio
- wixinstaller updated to require 4.6.2
- Library.Encryption changed to Standard2.0 so accommodate update to SharpAesCrypt
|
|
Removed System.Net.FtpClient and added the FluentFTP Nuget package which
is the new name of System.Net.FtpClient.
|
|
signals an update"
This reverts commit 4611ddab2a3050839f88059036b8b4360c33be5c.
|
|
an update
|
|
|
|
|
|
This makes it explicit at compile-time that these fields should not be
reassigned outside the constructor.
|
|
If one of these fields is accidentally reassigned, it's possible for
threads to be oblivious to an existing lock. By making the fields
readonly, we will be notified at compile-time if we inadvertently
redefine one of these fields.
|
|
being passed to another process.
This should also solve the issues with #3001
This fixes #2961
|
|
Using strong-named assemblies can cause difficulties with the GNU LGPL
license, which allows for one to recombine or relink their application
with modified versions of the code. While one solution is to share the
private key so that people can sign the assemblies themselves, this
would break the trust that is expected from signed assemblies. For now,
the easiest fix is to simply not sign the assemblies. Note that by
doing so, we prevent the code from being referenced from other signed
assemblies.
This also fixes an issue introduced in revision ba94d36a80 ("Added
auto-update for WindowsService and Service."), where the WindowsService
project (signed) referenced the AutoUpdater project (not signed).
We also removed instances of <SignAssembly>false</SignAssembly> to be
consistent with newly created .csproj files that do not contain the
SignAssembly element.
This was motivated by the discussion in issue #2814.
|
|
|
|
This fixes #2519
|
|
|
|
Needs some work otherwise the service will auto-update with a new sub-folder instead of autoupdate from the source folder.
|
|
|
|
This fixes #1768
|
|
# Conflicts:
# Duplicati.sln
# Duplicati/GUI/Duplicati.GUI.TrayIcon/Duplicati.GUI.TrayIcon.csproj
|
|
|
|
This also moved stuff around in some project files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Added the --auto-update option to the commandline to allow automatic updates.
Added a new Duplicati.Library.AutoUpdater.exe tool to work with updates, especially handy if the update breaks the install and for manual handling of updates.
|
|
|
|
|
