What is WinGup for Notepad++?

This project is the fork of WinGUp. WinGUp has been built for Notepad++'s need, but keep its functionality generic for being able to be used on any Windows application. With new built-in Plugins Admin in Notepad++, a more specific updater for Notepad++ is necessary. Hence this fork from the original WinGUp.

What is WinGup?

WinGup is a Generic Updater running under Windows environment. The aim of WinGup is to provide a ready to use and configurable updater which downloads a update package then installs it. By using cURL library and TinyXml module, WinGup is capable to deal with http protocol and process XML data.

Why WinGup?

Originally WinGup was made for the need of Notepad++ (a generic source code editor under MS Windows). During its conception, the idea came up in my mind: if it can fit Notepad++, it can fit for any Windows program. So here it is, with LGPL license to have no (almost not) restriction for integration in any project.

How does it work?

WinGup can be launched by your program or manually. It reads from a xml configuration file for getting the current version of your program and url where WinGup gets update information, checks the url (with given current version) to get the update package location, downloads the update package, then run the update package (it should be a msi or an exe) in question.

Who will need it?

Being LGPLed, WinGup can be integrated in both commercial (or close source) and open source project. So if you run a commercial or open a source project under MS Windows and you release your program at regular intervals, then you may need WinGup to notice your users the new update.

What do you need to use it?

A url to provide the update information to your WinGup and an another url location to store your update package, that's it!

How is WinGup easy to use?

All you have to do is point WinGup to your url update page (by modifying gup.xml), then work on your pointed url update page (see getDownLoadUrl.php comes with the release) to make sure it responds to your WinGup with the correct xml data.

How to build it?

• Step 1: You have to build cURL before building WinGup:

  1. Open VS2017 Native Tool Command for 32/64 bits. If you want to build for ARM, open a cmd, and run the following command:
     C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsamd64_arm64.bat
  2. go to curl winbuild directory:
     cd <your wingup source path>\curl\winbuild
  3. compile cURL by using one of the following commands, according the mode and archetecture of wingup you want to build.
     • x64 release: nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=x64
     • x64 debug: nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE=x64
     • x86 release: nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=x86
     • x86 debug: nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static DEBUG=yes MACHINE=x86
     • ARM64 release: nmake /f Makefile.vc mode=dll vc=15 RTLIBCFG=static MACHINE=ARM64

• Step 2: Open vcproj\GUP.sln with VS2017.

• Step 3: Build WinGup like a normal Visual Studio project.

To whom should you say "thank you"?

Don HO [email protected]