Questions about application deployment (squirrel)
I have a nearly finished WPF application hosted on a github repository and was wondering about deployment.Main goal is to have an .exe or .msi installer, where the user doesn't need to do anything difficult (like installing .net framework). Furthermore automated updates from the application would be nice, since I'm still working on it and have several features in mind, I want to implement. Having never done this before, after a bit of googling I come across squirrel and watched and followed this video from Tim Corey.However there are some issues:
- Using the
Setup.exeafter installation my app starts and closes immediately. Starting it from the bin folder in my project or via VS2017 debugging it works fine. - Being on github I wanted to use the option to update based on the releases on the repository. How to do that is described here and seems rather easy, however
UpdateManager.GitHubUpdateManager()seems to be not defined when I want to use it.
My best guess (but really only a guess) is that the problem lies with the version of .NET: My app uses 4.6.1 while squirrel seems to support .NET 4.5 (at least that's what I gather from the nuget packaging process).
The question here is: What are good alternatives, or solutions to my issues with squirrel? As Tim Corey points out in the video there are some new tools coming out from Microsoft directly? Seems weird to me that deployment of an application isn't more integrated into the whole framework.
0 comments:
Post a Comment