xaniffHello there. I'm writing a commercial plugin for a program and I need to be able to get updates to the users in the least complicated way. I came across wyUpdate and it really seems up my alley, but I wanted to make sure it would work in my case before purchasing it.
My program compiles to a DLL which is loaded into the main program at launch. Could wyUpdate do its whole updating magic if my program was just unloaded at some point and relaunched or is this just not a viable route for what I need? If not wyUpdate, does anyone know of anything similar or how I could go about providing updates to my plugin?
And on a side note, no, the developers of the main program do not offer any update interface for me to use myself. The only way they allow updates is if they have my source code and build/push the update themselves or through a manual user update process.
Thanks for any help ya'll can give!
xaniffNever mind, delete this thread please. After discovering the free trial, I decided to give it a go and it works fine. Even just having an update whenever the main program is reloaded is good enough for me. I'll definitely be buying this tool in the next couple of days.
My program compiles to a DLL which is loaded into the main program at launch. Could wyUpdate do its whole updating magic if my program was just unloaded at some point and relaunched or is this just not a viable route for what I need?
A few of our customers have similar needs to yours (a component of a larger app needs updating). It's not the common use-case, but it's certainly possible with wyUpdate. There are a few ways you can do it. Here are the 2 best ways to do it based on what little information I have about your setup:
Method 1
Install your app (and loaded dll) in a subfolder of the app that loads your dll. For example, if the "framework" app is "C:\Program Files\Frame", put your app files in "C:\Program Files\Frame\YourApp". If the "framework" app doesn't allow loading of dlls from sub folders then see "Method 2". Otherwise continue reading.
Use wyUpdate to silently check for updates. Then, if updates are found, tell wyUpdate to begin updating while simultaneously unloading your dll. After the updates to your app have installed, execute a script or some API to tell the "framework" app to re-load your newly updated app file.
Method 2
Silently check for updates using wyUpdate (or use the AutomaticUpdaterBackend if you're making a .NET dll), then when the updates are ready either prompt the user or, if you're using the AUBackend, install the update on the next start of the "main app".
This solution isn't as elegant as Method 1, but it works.
Tell me if this helps.
