You don't need to implement activation in the installer at all. It's completely optional, and it might be more consistent to only implement the licensing directly into your app.
It's completely up to you.
MSI distribution with activation codeSolved
dor@cligal.comHi, my clients want me to create an MSI for distrubting and activating the application on all the stations in the organzitions.
can you please direct me to how I should do it?I am using a c# WPF application, with INNO setup for creating setup files. I have implemented activation using the application, and ALSO using INNO setup. for creating MSI files I am using MSI wrapper.
dor@cligal.comI have implemented activation using the app, but the clients don't want the end-user to activate it one by one. they want to bundle the activation for all users with a single serial key. 🤔
That's why I wanted to use the MSI. but if there's a way to implement to bundle the activation for all users directly using the app, I can implement it that way. Do you have any suggestion?
We don't have a pre-built example of using activations in an MSI. But you can certainly do it. Google some variation of "calling DLL in MSI" and you'll find a thousand ways to skin a cat. Use the C API: https://wyday.com/limelm/help/using-turboactivate-with-c-plus-plus/
dor@cligal.comwhy should I use the c API? my application is in C#.
still stuck with that. would appreciate extra guidance if you can.
You might be able to use C# in the MSI. I don't know. Typically installers require a lower-level language. This might have changed.
Long story short: whatever languages MSI supports, and you're comfortable with, use that.
Have a look at WixSharp on Github. It makes MSI things much more C# friendly.