Closed jessemillar closed 7 years ago
@jcooklin referenced these in #2 and thought they were applicable more to this issue, so I'm copy/pasting it here:
Below are some high priority work items related to build and deploy as I see it:
- [ ] Start stubbing out Windows section in the README
- [ ] Create Windows Snap package (MSI)
- [ ] Install snap as a service
- [ ] What user does the service run as
- [ ] What kind of permissions are required
- [ ] Define where the default config should exist
- [ ] Define the appropriate config values for windows (where should logs go etc)
This tutorial looks good. Perusing now.
"The toolset is written in C# and requires the .NET Framework to run. However, this only applies to the toolset itself. The installation packages you create with the toolset do not require any extra framework or software to be installed on the target computer."
While I haven't verified these personally, these examples look promising.
@jcooklin Do we care about signing the MSI?
Development here.
Used the wizard above and in less than 10 minutes was able to generate a simple MSI which stuck the snap.exe into the Program Files directory. Haven't really looked into the other options yet, but WiX Edit seems promising.
On first glance, the WiX framework seems promising.