Cost Of Operations?: License Fees?

[ustk]

@d-healey said in Cost Of Operations?: License Fees?:

Also signing for AAX requires a dongle (iLok).

Oh yes for the signing procedure... Of course, I wasn't at it...

[aaronventure]

@ustk if enough people start your exe, defender will eventually stop throwing a warning. That's why I suggested an installer app for HISE where devs would just attach a payload. That way once it eventually got past the defender smart screen, it would stay so.

And it exists, check the Payload Installer in the tools directory of HISE. The windows one works, the one for Mac not so much. I'll probably be pesting Chris about it soon.

Also, you can just upload your exe files to the defender whitelist on the microsoft page (you gotta be logged into your Microsoft account), select that you're a developer uploading an app for whitelisting, and after 3 weeks it'll be whitelisted and smart screen shouldn't pop anymore. But 3 weeks is a lot, almost feels like shipping for PlayStation.

[DanH]

@aaronventure what page is this?

[bendurso]

@DanH I think is this one: https://www.microsoft.com/en-us/wdsi/filesubmission

[bendurso]

@aaronventure Can you submit installers made with inno setup?

[aaronventure]

@bendurso yes.

Keep in mind that every time you build a new installer, you'll have to upload it again and wait 3 weeks.

[aaronventure]

HISE/tools/payload_installer at develop · christophhart/HISE

The open source framework for sample based instruments - HISE/tools/payload_installer at develop · christophhart/HISE

GitHub (github.com)

This is an attempt to simplify the process for everyone. But the mac version won't load the payload.

[Christoph Hart]

@aaronventure said in Cost Of Operations?: License Fees?:

But the mac version won't load the payload.

It also won't write to the global library folder and other things. This is one of the things in HISE where the sunken cost fallacy is lower than the annoyances so I wouldn't recommend anyone to use that method.

[aaronventure]

@Christoph-Hart it doest need to, it just needs to run the packages installer you ship with it.

[Christoph Hart]

@aaronventure Hmm, so

1. Embed the .pkg into the payload
2. Run the payload installer
3. In the payload installer, run a shell script that launches the .pkg installer?

Haven't thought about that, but it gives strong "Yo Dawg I like you heard installers so I put an installer into your installer so you can install the installer" vibes...

[aaronventure]

@Christoph-Hart That's the whole point, because your shell says xattr -cr mypackagesinstaller and then runs it, which just tells the gatekeeper that the file is fine.