App update framework for Windows, inspired by Sparkle for macOS

This PR take part of solving issue #20.

It keep the way project where organized.

• New C# assembly project into WinSparkle-2013 and WinSparkle-2015 (WinSparkleDotNet)
• New WinForm example project into examples-2013 and examples-2015 (example_dotnet.csproj)

And try to correct most of the problems from pull #55.

This don't add the feature as unique DLL for C#. This will come after, if this is validated. Target WinSparkle API 0.5.X (from master)

It tested with Windows MinGW Qt 5.3.1 and Fedora MinGW. For MSVC 2010 I can't build. Probably support for MSVC can be added. But I haven't such wishes atm.

I'm trying out WinSparkle for a project, and it seems to have been working nicely until now, where I've had the following problem:

On update check, WinSparkle correctly reads the cast and sees that a new version is available. It doesn't, however, download the new version but instead installs the same old version that was downloaded for an earlier update.

Do you have any idea as to why this is happening and how to prevent it?

Compatible with Sparkle method of DSA signing and verification.

Uses OpenSSL and adds external dependency: libeay32.dll (but NOT ssleay32.dll).

Theoretically can be reimplemented, to use WinAPI only.

Reffers to #23.

I'm trying to display release notes published on a WordPress site that uses a fully responsive design. The release notes are displayed correctly on an iPhone and in Internet Explorer 11 when I resize to the width of WinSparkle's release notes control.

When displayed by WinSparkle, however, the release notes are not rendered correctly. The browser control shows a horizontal scrollbar and displays only about 60% of the page width. And the page is a bit blurry.

This does not happen with the plain HTML release notes based on which I created the WordPress post. No horizontal scrollbar is shown.

I'd be thankful for any hints on how this could be fixed (e.g., by configuring the control in a different way).

Updated the xml parser with a simple checker for whether criticalupdate tag is present at present, it only detects the tag in this form, though it can be extended to support the way sparkle 2 does with a bit of effort.

 <sparkle:tags>
     <sparkle:criticalupdate/>
 </sparkle:tags>

p.s. this does not parse the specific version string embedded in the criticalupdate tag. it also doesn't deal with the case where criticalupdate tag appears outside of sparkle:tags

On detecting this particular tag in the appcast.xml, the installer wizard will make the following changes to stateupdateavailable

• Hide the skip & remind me later buttons.
• Hide the close button on the title bar of the dialog box

Added win_sparkle_set_config_methods(), which can be used to override WinSparkle's default Windows Registry interface with custom functions, so users can provide their own functions when they want to manage all configuration by themselves.

I debugged into the source code, I think it was introduced in commit: Don't fail downloads on redirects to another server

In my case, it can easily go to line 355 !!

This happens on version > 0.5.2.

This PR fixes 302 redirects for our mirror system (http://mirrors.kodi.tv).

We are using the following appcast.xml (which you can use easily in your "example_psdk" for reproduction aswell): https://raw.githubusercontent.com/xbmc/SparkleBackend/fix_redirects_demo/sparkleupdate.xml

This announces this file for download:

http://mirrors.kodi.tv/test-builds/win32/KodiSetup-20170611-bb3345af02-sparkle-x86.exe

The mirrors are using mirrorbits and are redirecting to the actual mirror with a 302 found status. (URL redirection).

The dwInternetStatus in the callback when trying to download that file is as follows:

INTERNET_STATUS_HANDLE_CREATED INTERNET_STATUS_DETECTING_PROXY INTERNET_STATUS_RESOLVING_NAME INTERNET_STATUS_NAME_RESOLVED INTERNET_STATUS_CONNECTING_TO_SERVER INTERNET_STATUS_CONNECTED_TO_SERVER INTERNET_STATUS_SENDING_REQUEST INTERNET_STATUS_REQUEST_SENT INTERNET_STATUS_RECEIVING_RESPONSE INTERNET_STATUS_RESPONSE_RECEIVED INTERNET_STATUS_CLOSING_CONNECTION INTERNET_STATUS_CONNECTION_CLOSED <- this one is the Problem because in the original callback handler it closes the client side handle INTERNET_STATUS_REDIRECT INTERNET_STATUS_DETECTING_PROXY INTERNET_STATUS_RESOLVING_NAME INTERNET_STATUS_NAME_RESOLVED INTERNET_STATUS_CONNECTING_TO_SERVER INTERNET_STATUS_CONNECTED_TO_SERVER INTERNET_STATUS_SENDING_REQUEST INTERNET_STATUS_REQUEST_SENT INTERNET_STATUS_RECEIVING_RESPONSE INTERNET_STATUS_RESPONSE_RECEIVED INTERNET_STATUS_REQUEST_COMPLETE

This means we are operating on an invalid/closed handle after the request was completed and we try to download the file.

Closing the handle in the callback is not needed at all. Because of the destructor of the struct InetHandle will close the handle as soon as the InetHandle conn goes out of scope from the DownloadFile method.

This change allows us to use winsparkle for our project with the big mirror system as backend.

Thx for considering a merge.

Regards Memphiz of Team Kodi.

In using winsparkle with a qt application, I call win_sparkle_init() in the showEvent() of the main widget. But, winsparkle pops up behind my application. I am using Windows 8.1 x64 and Qt 5.3.2.

Detect download failures due to timeouts or network connectivity issues and throw an error (instead of erroneously showing the download as complete). Because these failures also return 'dwBufferLength = 0' like a successful download, we detect them by checking the number of received bytes against the Content Length (only if it is available). If there is a mismatch, an error is thrown. Otherwise, the download is considered successful.

We've been getting several BugSplat crash reports related to exceptions when showing the release notes. This is a pretty simple fix to catch those exceptions so that we don't crash.

Motivation: support building winsparkle on win arm64. Rough steps I took:

• Checkout a newer wxWidgets submodule
• Regenerate project using latest bakefile
• Update 3rdparty/wxWidgets_setup_h/wx/setup.h
• Fix compile errors by tweaking setup.h
• Fix link errors by including new files in wxWidgets.bkl
• Revert some configurations to fix https://github.com/vslavik/winsparkle/issues/138#issuecomment-410808382

Thanks for the awesome project, as sparkle for osx has a channel field that we can use for beta updates only https://sparkle-project.org/documentation/publishing/#channels . It would be great if we can have the same thing.

Add preliminary EdDSA validation support (partially closes #187 as signing is still missing). I tested with valid and invalid signature and it seems to work. Note that more testing is probably needed.

Some comments:

• Uses https://github.com/orlp/ed25519.git like the primary Sparkle project, causes minimal size increase of the final dll.
• Public key verfication is not there yet, I guess it is enough to just do the Base64 decoding + size check?
• Not sure I updated bakefile/vcxproj correctly. I get some errors, but it everything looks fine. The only thing is that the format changed a bit (I guess I'm using a different version of bakefile as the current files were generated with).
• Do we need that complicated file reading? I admit I took the first snippet from StackOverflow on how to read full files on windows.
• RC integration not tested (I'm not primarily a Windows developer, I'm just trying to port one of my apps to Windows).

Tagging @kornelski and @vslavik.

VCPKG is a C++ Library Manager for Windows https://github.com/microsoft/vcpkg It is driven by cmake and allows to integrate libraries with various build systems like msbuild.

I have crated a port for WinSpakles here https://github.com/microsoft/vcpkg/pull/17563

During the code review I have been ask to link against the libraries that are already build by vcpkg and not against the source 3rdparty library.

What is the best way to do it?

Is there a chance that the required changes are integrated here?

When win_sparkle_check_update_with_ui() is used to allow the user to manually check for an update (i.e. via a menu item), the flow is the following (assuming an update is available):

1. Click menu item to check for updates
2. WinSparkle dialog shows that a new version is available
3. User clicks "Install update"

4. Update starts downloading
5. After download is complete, the user must then again click "Install update"

This PR allows the additional (and maybe redundant?) confirmation at Step (5) to be skipped and the update to be automatically installed after downloading, via an arg: win_sparkle_check_update_with_ui(1);

This is achieved in code by using two flags for the auto logic: one each for download and install