few basic questions

Hi sorry if these questions have been asked before, perhaps if they are common questions make a sticky. OK here goes:

1) What is the difference between wyBuild and wyUpdate?2) Will this software allow a windows service the ability to update itself, without user involvement?

3) The updater is a cool tool but how did the user get the software on the computer in the first place, i.e. what installers are people using together with your product?3b) Some installers include updaters, so besides the deep c# integration your software offers, which is very cool, are there any other advantages for your updater?3c) Does this software have an install partner?

4) If the application is installed with an msi, will uninstall work properly, presumably in the msi uninstaller I can run a command to remove the app folder, which would do the job.

5) I understand there is a new version which is due to arrive imminently, what new features will it have?

6) (Side question) I need to ask the user during the installation if the user would like to install a SQL database, if the user chooses yes then I download and install SQL Express 2005, is there an easy installer which would allow me to ask this question?

Many thanks for answering these questions.

Hey David,

1) What is the difference between wyBuild and wyUpdate?

With wyBuild you design and build the updates. wyUpdate, on the other hand does the actual updating. wyUpdate is the part you include with your application. The wyBuild installer (download it here) contains everything you need to start delivering updates of your apps to your users.

2) Will this software allow a windows service the ability to update itself, without user involvement?

This is a heavily requested feature that's coming in the next version (2.6.11). We're trying to get it out before the end of the week. You can start/stop services, install new services, and update services now, however it won't be completely silent. In wyBuild 2.6.11 you'll have the ability to update completely silently.

3) The updater is a cool tool but how did the user get the software on the computer in the first place, i.e. what installers are people using together with your product?

As we cover in the step-by-step walkthrough article, we recommend 1 of 3 installers: NSIS, Inno Setup, or WiX. We use NSIS for wyBuild's installer and you can use WiX to make MSI installers.

Making installers from wyBuild will be possible in the short term. I can't put a date on it yet, but it's before the year is out. We will probably include WiX with wyBuild and just make it a "one-click" operation to make the MSI installer.

3b) Some installers include updaters, so besides the deep c# integration your software offers, which is very cool, are there any other advantages for your updater?

Yes, wyBuild, wyUpdate, and the AutomaticUpdater have many advantages over the limited updaters included with "professional" installation creators. The limited pseudo-updaters included with some install creators are simple bootstrappers; that is, they check for an update then they download the full exe or msi installer and just run it.

wyBuild, on the other hand, compares versions of your app and generates the smallest possible patch from the old version to the new version. This can save you big on bandwidth bills. Plus your customers will be able to get the updates faster. There are a thousand other advantages.

3c) Does this software have an install partner?

No, we don't recommend any "professional" installers. Mostly because all of the good installers are open source: NSIS, Inno Setup, or WiX. Microsoft uses WiX to build installers for a large portion of their software and NSIS is used by Mozilla (among others). In short, these aren't lightweight installers. They're trusted by small and large companies alike.

Eventually we'll integrate WiX in wyBuild to simplify the whole process.

4) If the application is installed with an msi, will uninstall work properly, presumably in the msi uninstaller I can run a command to remove the app folder, which would do the job.

Yes, there's a wyUpdate command ("wyUpdate.exe /uninstall") that will uninstall any newly added files, folders, registry, etc. You can call that as part of your MSI uninstaller and everything will uninstall cleanly. We can point you in the right direction if you need help.

5) I understand there is a new version which is due to arrive imminently, what new features will it have?

AutomaticUpdater that works in non-UI apps (Windows Services, console apps, etc.), silent wyUpdate options for updating non-.NET Windows Services, various wyBuild improvements, etc.

It's a "minor" upgrade (i.e. it's free for all our users).

6) (Side question) I need to ask the user during the installation if the user would like to install a SQL database, if the user chooses yes then I download and install SQL Express 2005, is there an easy installer which would allow me to ask this question?

There are lots of ways to do this. If you're using WiX, here's an article that shows how to detect whether it's installed or not: "How to detect SQL Server Express in WiX installer".

Many thanks for answering these questions.

No problem. If you have any other questions don't be afraid to ask.

Thank you for your answers, should I wait until version 2.6.11 to get started, will there be any breaking changes?

Nope, no breaking changes.

Has the new version that supports silent automatic updates for windows services been released? I have an immediate need to integrate an auto updater with an existing WCF service and would like to trial this tool.

We already have a windows installer project that creates an MSI that is released to customers. In order to use wyBuild, must we modify our existing installer package so that the Add/Remove Programs un/installer works with any patched versions?

I hope to demo your tool soon!

Has the new version that supports silent automatic updates for windows services been released? I have an immediate need to integrate an auto updater with an existing WCF service and would like to trial this tool.

We've just finished it and we're releasing it Monday.

We already have a windows installer project that creates an MSI that is released to customers. In order to use wyBuild, must we modify our existing installer package so that the Add/Remove Programs un/installer works with any patched versions?

You have to add wyUpdate.exe and the client.wyc files generated from wyBuild and include them with your installer (see the step-by-step walkthrough). In your uninstaller simply "wyUpdate.exe /uninstall" to uninstall any newly added files, folders, registry, etc.

That's great news. Will you also have a trial of the new version available today?

No, but you can get a trial extension by emailing us at support@wyday.com and we'll send you one.

wyBuild 2.6.11 is now out. If you need a trial extension just send us an email at support@wyday.com.

Our testing went very well with the existing service project. Thanks for your help.

I have just purchased the full version of your software. Are there any steps that need to be taken to transition from the trail to full license other than putting the key in the wyBuild app? Do we need to rebuild the project we have been demoing with new client, updater, etc. files, or does licensing not affect the client files and DLL's?

Hey Doug,

Are there any steps that need to be taken to transition from the trail to full license other than putting the key in the wyBuild app? Do we need to rebuild the project we have been demoing with new client, updater, etc. files, or does licensing not affect the client files and DLL's?

All files you build with the wyBuild trial are unaffected -- just enter the product key. The only limitation to the wyBuild trial was the amount of time you could use it (21-days).

I have created one installer using inno setup compiler. Which is based on Access file(Application.accdr). Main database is located in share drive. So how can i update this access database in user machine.Can you please let me know with clear step by step process for update things.

Thank youArun

1. Is the database installed by the installer?2. Where exactly is it installed?3. Will each of your customers have a copy to this access database?4. Is the database read/write or read-only?

In short, I need a whole bunch more information.

If the database is installed to any "built in" folder on Windows, then just use the corresponding folder in wyBuild (e.g. "Your program's folder", Common Files, etc.)

1) Yes tha database installed by installer in Programfiles.2) It is installed in Program files by default.( user can change installation path if they want)3)Yes in each user system this accdr file is installed but main database is located in Share drive.4) The data base is Read/Write.

I need to give Download sites. Can i use my share drive address for this?Can i use same address for Upload the Updates?Could you please tell me the detailed update process because iam little bit confuse about sites(FTP or Http or sharedrive)

How wybuild will update my application.accdr file which is installed in program files and how is compares with main database which is located in sharedrive?

Thanks

An accdr is just your application. You update it like any other application. See: Walkthrough for your first time using wyBuild.

In the accdr file with any other files in your app to the "Your program's file" folder in wyBuild. Follow the step-by-step walkthrough for how this works.

After reading that and trying it for your own app, if you still have any questions I'll be glad to help.

Do i need to use source code for updating accdr file? and little confuse with Download sites and Upload the updates? Can i use same sites for both download and update? Sorry if you get irritate with my questions am new to this wybuiild. So kindly let me know the details clearly....Thanks

An download site is where the updates are downloaded from. The upload site is where the updates are uploaded to on your server. They probably correspond to the same location on your server, but you'll almost use different user/password for downloading and uploading.

That is, you don't want your end-users to have write-access to your server, so you might use an http:// or an "anonymous" ftp:// site for the download site. For example: http://yoursite.com/updates/%file%.

For the upload site you need write-access to your server. For example: ftp://username:password@yoursite.com/updates/

Should i add my application files which are from programfiles? Do i need to add these files in to Your Program's folder in Wybuild?

You need to make a copy of *all* the the files that consist of your application. See Step 6. in the step-by-step walkthrough.

When i run wyUpdate.exe am getting message like An error occured: unable to check for the update, the server file failed to load (the remote server returned an error: (530) Not logged in). But i am able to Upload updates to the server and giving message upload updates successfully. Could you please help me to avoid the error?

I take it you're using an FTP site for the download site? If so, you've probably forgotten to specify the username and password.

for example:

ftp://username:password@yoursite.com/updates/%file%

Do i need to run wyupdate.exe manually for my installer(which is built using Inno setup compiler) or is there any automatic updates will be possible?

You run wyUpdate.exe from your app. You can either just simply execute wyUpdate.exe or use any of the commandline arguments to do cool things like silent checking, etc. See: How to Silently Check for Updates.

HI Wyatt..I have done with creating updates to server and now i want to download the updates from server in to user machine. So what is the process here to run updates in to user machine?

Well, that's what wyUpdate.exe does. So double click that program. It will check for updates, and if there are updates, it will let you install them.

In your app you can programmatically start wyUpdate.exe. Does that make sense?

Wyatt, I can add Wybuild.exe to my installer. Whenever i install my installer then only i can run wybuild.exe else other time how can run updates in user machine by user.

You don't include wyBuild with your app (that's the program that builds the updates). You do include wyUpdate with your app (that's the program that updates your app).

In your Ms Access application you can run wyUpdate.exe using the shell() Visual Basic function. Google around for examples on how to use Shell().

Yes i include wyupdate.exe.

in my application i created installer using Inno compiler script. iam not working with Access application. i have taken accdr file only.So i cant use shell() in VB. Is ther any other way to run updates?

Yes, create a shortcut to wyUpdate.exe somewhere and have your users double click that.

Can't we run wyUpdate.exe silently instead of double click on that?

Yes, if you have a program to run wyUpdate, you can run it silently. Otherwise you need to user to run wyUpdate.

Do you have a program you're installing to your customers' machines, or just a database file?

I dont have a program. Iam installing just a database file along with some supporting files.

Ok, then create a shortcut to wyUpdate.exe and have the user click that when they want to update your files.

Hi Wyatt,

As per your sugestion i created a shortcut on desktop and running updates fine. Here my requirement is i want to replace a new file (updated) in place of old file with same name. So can i update that?

Yes, you can update files. That's the whole purpose of wyBuild. See: New release workflow

I have installed 1.1version of my installer in user machine included wyupdate.exe and client.wyc file.Created shortcut for wyupdate.exe. Iam changing my version to 1.2. So here do in need to install my installer everytime aloong with new wyupdate.exe and client.wyc.????? or can i run my shortcut directly with out installing installer??

Is client.wyc comparing version with wyserver.wys file?? because in my first installation client.wyc stored 1.1version then again do i need to add client.wyc 1.2 version to my installer or not?

So here do in need to install my installer everytime aloong with new wyupdate.exe and client.wyc.????? or can i run my shortcut directly with out installing installer??

The installer is just if you're distributing your app to new users. If you're not doing that, then you can just push your updates using wyBuild (to make the updates) and wyUpdate to do the actual updating.

Is client.wyc comparing version with wyserver.wys file?? because in my first installation client.wyc stored 1.1version then again do i need to add client.wyc 1.2 version to my installer or not?

wyupdate automatically modifies the client.wyc file when you release an update.

Wyatt,

Thanks for bearing me. Now iam looking for silent updates. I have to run my wyUpdate.exe silently and updates should be downloaded directly to user's machine with out their involvement.

You can do silent updates a few ways. You can call wyUpdate within your app (if you've decided to deploy one alongside your other files). See: How to Silently Check for Updates.

That's a good place to start.

Hi,

In my application i have called wyUpdate.exe using SHELL. But in this i want to update based on conditions 0,1,2. Here iam running update when user open(run) the application.So i need to run the application when only updates are available.if there are no updates then wyUpdate should not run.

present iam using code like this.

ptsApppath = CurrentProject.Path & "\wyUpdate.exe /quickcheck"varProc = Shell(ptsApppath)

Can you please provide VBA code for this to run updates only updates are available with user permission and no need to run if updates are not available...Thank you.

Google will help you figure out how to use the Shell() function to get the return codes (for example: Shell Function).

For everything else, see our documentation. Specifically :How to Silently Check for Updates.