So what is this AutoPatcher thinguy anyways?

Glad you asked.

This was initially presented here by Richard Preziosi, but has since been revamped and rebranded.
You can go there and read on a few of the more technical aspects of the process if you want. It's still pretty much accurate in that respect.

Go on, i'll wait...

Back? Good, let's continue then.

The AutoPatcher is a bundle pack with the patch maker app (AutoPatcher) and our own WLE updater library (AutoUpdater), that you can use to keep your customers up to date on the latest and greatest release of your software, be that a bug fix or an upgrade.

Here's how it works

First you use the AutoPatcher to create your update project. You feed information into two basic forms about your studio and the app your about to release, press a button and you get a log generated for you.
You than place that log and the apps files online somewhere.

Next it's time for the AutoUpdater. The AutoUpdater is Net library, but don't worry, when you buy it you get a demo WPF app to give you a boost on this step. It's just about ready to use actually.
So you take that demo, XAML it into whatever look fits your app most, put some values in a couple of properties, add whatever else you want and what you get is na updater/launcher for your app.
If you ever played na MMO you know what i mean by that.

So now, finally, you just send your customers the launcher with the Updater Library and it takes care of getting your app from your online repository into your customers computer, ready to run.
Next time you want to update it, just generate a new log file, place the new log and new files online and the AutoUpdater takes care of things for you client side.

It's actually a lot simpler than it sounds. Trust me.
Plus you'll get a step by step User Guide with it that probably goes way too deep on some aspects than it would probably be needed, so it's highly unlikly you'll ever have a problem with it.
We really tried to make the process fool proof.

Simplicity has an... interface

Just look at this cool and sleak interface if you don't believe me. That's the most complex form of the two you'll need to fill and as you can see, one of the fields automaticaly takes the value from the other form and most of the form's space is taken by the Update Notes area, which, by the way, is actually optional.

There's no words to explain how simple we made this for you.
The user guide itself will go with you field by field on every form, and lists one by one every event, method and property on the library. Plus goes with you step by step in taking the demo laucher and making it work for your app. That's how simple we made it for you.

Sure, creating the launcher itself takes a bit more effort, but most of the job regarding the update process is done for you in the demo we will be providing, and most of the remaining work is actually you changing the interface of the launcher in XAML to customize it to the look you want - so actually it's as much work as you want it to be.

So when is it coming out?

Really soon. In fact, right next month.
We're aiming at releasing this and OneWorld at right about the same time. So keep an eye out for both this products and more coming your way from our studio.

Hope you enjoyed knowing a bit more about this product and get as psyched as i am about it.

Leave any questions and comments below and i'll answer as i can.