Absolutely true, but that isn't what happened (at least, not yet). Most companies found the fee reasonable and worth it to have us maintain the project and not have to fork it.

▲

ApolloFortyNine a day ago | parent [-]

>Most companies found the fee reasonable and worth it to have us maintain the project and not have to fork it.

You must have incredibly good analytics to know exactly what companies are using your nuget package. Did you embed a phone home?

	▲	vpq a day ago \| parent \| next [-]
		WiX usage is easy to check, just open an installer with Orca, and you'll see a bunch of WiX artifacts. Checking whether it's their own compile or official binaries is also simple if they use an extension like the official Util one, which many do: It embeds a binary that implements the custom action, which is signed by FireGiant. As for turning this into analytics / statistics, I imagine you could just download every MSI from winget and just check if they contain a FireGiant-signed extension dll.
	▲	robmensching a day ago \| parent \| prev \| next [-]
		I was specifically talking about the companies paying the Fee and the feedback I got from others who don't use the WiX Toolset but understand Open Source and the problems facing maintainers. But it is easy to tell when an installation package is built by the WiX Toolset (or any other tool) when you know where to look.
	▲	notpushkin a day ago \| parent \| prev [-]
		If this is about WiX, I think it’s easy to just spot their installers in the wild.