Which option is best

Hi,

after doing a successful test app with AutomaticUpdater I think I am ready to add this feature to one of my current projects.

The questions that I have now are which options to choose, you see, my current project does not contain a menu but instead it has buttons that call the functions for displaying the Help file, About form & Settings form. It also has a button that currently checks for updates but this is done by opening the browser to a specified page on my website where the client can manually check for a version update, download and run a patch.

This manual process is what I would like to automate, hence using wyBuild etc...

I have read a post on this forum where another user was calling the AutomaticUpdate that was located on a separate form via a button press and it seemed somewhat problematic.

This could be an option for me, or another way would be to just call the wyUpdate via the button press. If I chose this second option, would I need to include the AutomaticUpdate.dll with my app?

Any pointers would be greatly appreciated.

Regards..,

Kirk.

Hey Kirk,

I have read a post on this forum where another user was calling the AutomaticUpdate that was located on a separate form via a button press and it seemed somewhat problematic.

It's certainly a lot more work to put the AutomaticUpdater on a separate form. I don't know the exact layout of your app, so this advice will have to be amended to fit reality, but here's how I recommend you use the AutomaticUpdater in your case: Have the AutomaticUpdater on your form (in the top right corner, out of the way). Also, either eliminate the "Check for updates" button (if you're running tight on visual space) or, if you're keeping the button, reprogram it to check for updates something like this:

if (autoUpdate.UpdateStepOn == UpdateStepOn.Nothing){    autoUpdate.ForceCheckForUpdate();}

Does this help?

Hey Kirk,

I have read a post on this forum where another user was calling the AutomaticUpdate that was located on a separate form via a button press and it seemed somewhat problematic.

It's certainly a lot more work to put the AutomaticUpdater on a separate form. I don't know the exact layout of your app, so this advice will have to be amended to fit reality, but here's how I recommend you use the AutomaticUpdater in your case: Have the AutomaticUpdater on your form (in the top right corner, out of the way). Also, either eliminate the "Check for updates" button (if you're running tight on visual space) or, if you're keeping the button, reprogram it to check for updates something like this:

if (autoUpdate.UpdateStepOn == UpdateStepOn.Nothing){    autoUpdate.ForceCheckForUpdate();}

Does this help?

Thanks Sam.

I got it sorted by excluding the AutomaticUpdater altogether from my form and calling wyUpdate from a button click like this:-

private void btnTbarUpdate_Click(object sender, EventArgs e)        {             System.Diagnostics.Process.Start(Application.StartupPath + "\\wyUpdate.exe");        }

I have tested it out and it works great.

Thanks for your help.

Regards..,

Kirk

Hi,

just one other thing I have noticed, BBCode is turned off so my posts with Quotes look a little messy and the 

 function cannot be used.


I have looked in my User Control Panel but in there it shows as BBCode is switched on.


Is there a reason why I cannot use BBCode?


Regards..,


Kirk
Is there a reason why I cannot use BBCode?

We had to disable it for everyone except us here at wyDay because we get massive amounts of spam. Unfortunately phpbb doesn't offer granual control over certain BBCodes (e.g. just disable images and links), so we had to disable all BBCodes.

We're replacing phpbb with a proper solution that actually filters spam.

That sounds pretty fair but slightly concerning for me as I have just installed phpBB3 today.

Mmm, maybe a rethink before I get too involved with themes etc...

Regards..,

Kirk

Reply
Discard post