wix3
au
wix3 | au | |
---|---|---|
45 | 4 | |
2,109 | 220 | |
0.8% | - | |
5.5 | 4.3 | |
about 1 month ago | over 1 year ago | |
C# | PowerShell | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wix3
-
How to create an Installer for a Winforms application using Wix for Visual Studio 2022
We also need to install WiX Toolset v3.11.2, you can download the latest version from here
-
Twenty years maintaining the WiX Toolset
For those like me (I never used Windows) who do not know WiX; https://wixtoolset.org/.
-
Creating a windows service application
I don't do Windows installers myself, but I hear WiX is popular: https://wixtoolset.org/
-
Win32 App Isolation
I actually like WiX[1] — it has a bit of a learning curve, but, so long as I'm building on Windows and don't stray far from the default UI flows, I haven't found an easier tool for creating Windows installers as part of a product build process, especially those that require Windows-specific bits like COM component registration, Windows service management, setting restrictive ACLs on installed components, etc.
And while I'm not aware of any way to sandbox Windows Installer itself, I'm curious if AppContainer isolation can be applied to applications and services installed via MSI, which would still be quite useful even if the installation process itself is unrestricted.
Alternatively, now that MSIX supports service installation[2], I wonder whether an MSIX including a Windows service and a collection of client applications can be configured so everything runs within one AppContainer, isolated from the rest of the system, and whether permission to access specific external directories chosen by users in a configuration GUI can be transparently (to the user) delegated to the related service.
Alas, none of this is useful to me until it's compatible with at least the most recent version of Windows 10, as very few of my customers are running Windows 11, and I suspect many won't upgrade until Windows 10 is no longer supported (optimistically; as of last year, I was still getting occasional support requests from customers running older versions of our software on Windows Server 2003 R2).
[1] https://wixtoolset.org
[2] https://learn.microsoft.com/en-us/windows/msix/supported-pla...
- [Windows] Looking for open source program made to install other archived programs and create uninstaller for them
-
packaging games
For Windows, in the past, I’ve used the WiX toolset to create installers (https://wixtoolset.org/).
-
Can I publish and release a .NET Service with an installation executable on GitHub?
https://wixtoolset.org/ should be able to help you out there.
-
How to slipstream NVMe drivers into Windows 7 ISO [Tutorial]
Wix toolset to extract .exe to get the driver or .msi https://github.com/wixtoolset/wix3/releases
-
Production C++ software guide
For windows - store: https://developer.microsoft.com/en-us/microsoft-store/register/ - requirements: https://learn.microsoft.com/en-us/windows/apps/publish/publish-your-app/app-package-requirements?pivots=store-installer-msix - alternatively you can make MSIs and distribute them through your own website or another service. https://wixtoolset.org/ - publishing with chocolatey isn't a terrible option to help users with upgrade/installation automation. https://community.chocolatey.org/packages
- ReactOS
au
-
So according to Repology, Nix has an insane lead on available packages, but somehow has around a tenth of AURs maintainers. How does Nix also manage to be the most up to date?
I created au framework for chocolatey (Windows OS) and on packages that are cross platform, it made choco above Arch on freshness: https://github.com/majkinetor/au
-
Is there some centralized source to get the most recent version numbers of often used software?
Having said that, you may want to look into the source code for each package you're interested in. Many of them use the Chocolatey Automatic Package Updater Module, and had to solve this exact problem in some way to help automate updates. I've seen approaches varying from scraping a web page, querying an API, or even downloading the binary and looking at its FileVersionInfo struct.
-
Novice to Package Managers, Interested in Chocolatey
There are a lot of packages out there where you can customise the install location. If you want to automatically fetch from suppliers and create your own packages then you probably want to look at the automatic package updater with AppVeyor: https://github.com/majkinetor/au/wiki
-
WinGet is terrible. I want AppGet back
> I mean, it is a chocolatey, because they allow multiple packaged for the same software.
I think this is more healthy then having one with maintainers refusing to do stuff you may need. The real thing would be for vendors releasing packages but we are far from that in Windows land.
> I meant that packages are often not updated by the maintainers.
Yeah, that was the problem far more before then today. I created AU to solve that issue [1].
[1]: https://github.com/majkinetor/au
What are some alternatives?
winsparkle - App update framework for Windows, inspired by Sparkle for macOS
oneget - PackageManagement (aka OneGet) is a package manager for Windows
wixsharp - Framework for building a complete MSI or WiX source code by using script files written with C# syntax.
Versions - 📦 A Scoop bucket for alternative versions of apps.
NetSparkle - NetSparkle is a C# cross-platform software update framework for .NET developers compatible with .NET 4.6.2/.NET 6+, WinForms, WPF, and Avalonia; uses Ed25519 or DSA signatures! View basic usage here in the README or visit our website for code docs.
ChocoButler - ChocoButler - an automatic updater for Chocolatey
BruteShark - Network Analysis Tool
OSD - OSD Shared Functions
algorand-windows-node - Algorand Node Microsoft Windows support
ts_block - Blocks IP addresses generating invalid Terminal Services logons