Background Updating

We already support updating services from services (see: How to Silently update a Windows Service), but we welcome any improvements.

That's in wyBuild, which doesn't appear to be open source. wyDay has many of the features we're looking for, but there are some gaps. Do you offer consulting services to help fill those?

The help article is for wyUpdate. wyUpdate does the actual updating. wyBuild just creates the updates. But you don't even need to use wyBuild to create the updates. If you have time to spare (and are a glutton for punishment) you can build the updates by hand by using the file specifications.

To tell you the truth, I am a bit concerned about a custom solution becoming a black hole.

Maybe there's some way to use the built-in wyBuild functionality. The main challenges I see are 1. Reporting back to Central on the update status of all machines2. The ability to pick and choose the machines that receive a particular update.

I could spec out what we need, and send it to you, if that's something wyDay might take on. I'm sure your company, being familiar, could craft something in half the time we could. The new functionality would stand a better chance of becoming part of the core product too.

Some of the things you list we do plan to do, some we already do, some we plan to make easier, and 1 we will never do:

- Keep a database of the client machine names, along with their version history

But we're always happy to accept outside development.