search

drewnoakes / string-theory

Identify and reduce memory used by duplicate .NET strings
Other
297 stars 10 forks source link

Investigate distribution methods (e.g. ClickOnce) #8

Open drewnoakes opened 5 years ago

Thieum commented 5 years ago

Consider Squirrel for auto-updates instead of ClickOnce, and Chocolatey for first-time install.

drewnoakes commented 5 years ago

@Thieum thanks for the suggestions. Why would you recommend those over ClickOnce which takes care of both tasks at once?

Thieum commented 5 years ago

@drewnoakes ClickOnce is embed in the build process, which means a specific full build to create the clickonce setup, instead of just taking the output of the build and packaging it in a separate task. And also the signing part which is annoying in ClickOnce. Not sure .net core 3.0 will support click once out of the box either. Squirrel has integration with Github too: https://github.com/Squirrel/Squirrel.Windows/blob/master/docs/using/github.md There's an option to build an msi as well. I find it covering more scenarii than ClickOnce with a more modern approach to the build process (segmented part of the packaging with build -> result/artifact -> packaging -> publish).

As for Chocolatey, It's just make it easier for dev machine setup automation, and adds to the discoverability of the tool. Unless you consider the windows store as an alternative :) (I mean, you could, Nuget Package Explorer is there) Chocolatey could work with clickOnce I think, it's more a matter of discoverability and automation.

aolszowka commented 5 years ago

Regardless of the distribution method chosen, can you please keep a zip drop? Those are useful for us.

Perhaps investigate the logic used by ILSpy (https://github.com/icsharpcode/ILSpy)? They still zip deploy but have an update checker which is useful.