We are working on an automated solution for packaging builds and updating on-premise servers.
our customers are slowly moving to the cloud, but for now, majority are local. We are servicing WFC web services, migrating to MVC and Web.Api over the next year or more.
Is Wybuild a packager, an installer, or a deployment tool?
As I understand it the Automatic Updater works with WyBuild, but where exactly does Wybuild sit in the ecosystem?
We have a setup file using innosetup. Doe this replace that, or does it work with that setup file (i.e. will it patch across two setup files, or does it need a deployed application)?
So much is made of the auto update and the patching capabilities on the site that I cannot find any info on how it figures against installers and deployers, or whether it is both or neither.
So in an ecosystem using VSO Team Services that is currently producing successful inno setup files at the conclusion of the build, how does Wybuild fit in?
i'm looking for something that will handle deployment and auto-updates. Where deployment is the configuration step following the basic file copy done by Inno Setup. It seems we could use inno setup to deploy initial DB schema and initially configure the web.config, followed by what??? That's where I just don't see how Wybuild works together or replaces inno setup.
Thanks for any links to tutorials or other info...I'm just not finding the info I'm looking for.
Michael