Wybuild
Author: v | 2025-04-23
About wyBuild, wyUpdate, the AutomaticUpdater. Overview of wyBuild: An overview of wyBuild including some of the more prominent features. Features in wyBuild: A summary of the most useful features in wyBuild. Changes in wyBuild wyUpdate : The complete list of changes to wyBuild and wyUpdate since the first publicly released version. wyBuild. wyBuild is the complete automatic updating patching solution. Included in the wyBuild installer is wyBuild (to design build updates), wyUpdate (the open source updater program), and the AutomaticUpdater. Download wyBuild (latest changes). Learn about wyBuild LimeLM
wyBuild - basic information, download wyBuild
이 페이지에서는 .wyc 파일 확장자에 대해 자세히 살펴 보겠습니다..wyc 파일 형식이 정확히 무엇이며 어떻게 사용할 수 있는지 설명해 드리겠습니다. 이러한 유형의 파일에 대해 더 자세히 알고 싶다면 해당 파일을 찾을 수 있는 위치를 알려드리겠습니다. 또한 .wyc 파일을 다른 형식으로 변환해야 하는 경우 변환 방법에 대한 몇 가지 팁도 알려드립니다.이 파일 확장자와 관련된 2개의 파일 형식을 살펴봅시다!콘텐츠wyBuild Version DatawyUpdate Compressed Client Data저희 웹사이트가 여러분에게 유용한 정보를 제공할 것이라 믿습니다. 궁금한 점이 있으면 언제든지 문의하세요!wyBuild Version DataThe WYC file belongs to the Data category and works with wyBuild, being used as a wyBuild Version Data. wyBuild is a utility that gives developers the ability to create software update patches and distribute them to their user base quickly and easily. The developer is still actively supporting the wyBuild, likely. Our data shows that wyBuild uses 3 more file types.프로그램 이름: -마임 유형: application/octet-stream별칭:-관련 확장 프로그램:.iuc wyUpdate Client Data.udt wyUpdate Update Details FilewyUpdate Compressed Client DataThe WYC file belongs to the Data category and works with wyUpdate, being used as a wyUpdate Compressed Client Data. wyUpdate is the open source updater that's included with wyBuild. wyUpdate checks for updates, downloads any that are available, and safely updates your program. The developer is still actively supporting the wyUpdate, likely. Our data shows that wyUpdate uses 2 more file types.프로그램 이름: -마임 유형: application/octet-stream별칭:-관련 확장 프로그램:.wyc wyBuild Version Data.wyp wyBuild Project.wyc 파일 확장자는 단일 유형의 파일에 속할 뿐만 아니라 이를 사용하는 다양한 종류가 있을 수 있습니다. .wyc 확장자를 가진 파일에는 다양한 콘텐츠 유형이 포함될 수 있습니다. 이 확장자에 대한 유용한 정보가 있으면 저희에게 알려주세요!.wyc 파일 확장자의 철자가 잘못되었을 수 있나요?데이터베이스에서 다음과 같은 유사한 확장자를 발견했습니다:.qyc Quantec Yardstick Plugin.dyc Xerox Printer Driver Configuration Data.wtc WaveThunder Configuration Data.wc WorldCraft Data.yc YAC Compressed.wyc 확장자는 자주 잘못 사용됩니다사람들은 때때로 .wyc 파일 이름 확장자를 혼동하는 경우가 있습니다. 지난 한 해 동안
wyBuild Download - Use wyBuild to make update
With wyBuild you can deliver updates of your software to your users fast. No confusing interfaces - just simplicity.Make your users happy by keeping them up-to-date. They'll love having the latest bug-free versions of your software. They'll talk far and wide about how great your software is.Make your current users happy, attract more users, and make more money all with wyBuild.New Features:wyUpdate & wyBuild now support multiple languages. wyUpdate automatically detects the culture of the system, and selects the right language.Patching your files is now faster (especially for large files)Verifying downloads is now faster.Allow *.bat and *.cmd files to be executedAdd passive & active FTP transfer to the uploader.Add passive & active FTP transfer to the uploader.Increase the speed of the FTP uploader.wyUpdate now runs as a single instance (that is, only one instance of wyUpdate can update your product at once)Version comparison algorithm is now fasterNotable Bugfixes:Updated wyBuild to be easily understood by new users.Add proper support for unicode filenames and paths in updates.The file folder browser rejected unicode text when pasted in as a file or folder name.Languages that are only partially complete are now loaded correctly.Versions with "release candidate" are now parsed correctly.The menu items now look like system menus on Pre-VistaThe product key is now detected if it's entered in the installer.Cleaned up the administrator checking code - making it slightly faster.Increased the wyUpdate icon size in Windows 7 taskbar (so it no longer looks blocky)wyUpdate now gracefully handles corrupt self-update server files.Plus much more.Open SourceThe wyUpdate is open source (using the BSD license). Download the source and begin hacking away. It's C# 2.0 code.The wyBuild 14-day trial last for 14 non-consecutive days. That is, you can use wyBuild for once a month for the whole year and still have two trial days left. Or you can use it for 14-days in a row. It's your choice. This trial has no limitations and no popup-nags.If you need help, the wyBuild Help explains the harder to use features. Also, feel free to post any questions, suggestions, or bug-fixes. (No forum registration is required.)Here's a short video introduction to wyBuild ➡ Download wyBuild 1.3 now.Feb 28, 2009wyBuild .1 (wybuild-setup.exe) Windows Download and
We have a VB .NET application with the Automatic Updater control implemented for our customers to "Check For Updates". For application patches this works find. But with our next release we need to implement some schema changes in the M/S SQL database (add columns in some of the tables and add new tables). This M/S SQL database is shared by all of the client systems at a site. Here are two questions:1. We can include the SQL scripts to make the changes to the M/S SQL database in the WYBuild update process, per your notes on this topic. However, only the first client system at each site should execute this update. All the remaining ones should only upate the application code, since the shared M/S SQL database is already changed. 2. Once the M/S SQL database is updated, all of the client systems need to be forced to update the application before they are run again. The old application will not work with the new schema.We are not sure how to use WYBuild to implement this process.Oct 5, 2011This is an interesting question. There's no one right way (there are many, many options). Here's what I would do:The critical thing you have to do is to store the schema version in the database. Then everything else become relatively easy. So when you write your SQL script to update the database you can have a simple WHERE statement that aborts the process if the schema version is not X.2. Once the M/S SQL database is updated, all of the client systems need to be forced to update the application before they are run again. The old application will not work with the new schema.Again, this is where the schema version in the database comes in. When your application starts (or maybe everytime your app makes a SQL query) check that schema version value. If the client is not compatible with schema version X you can forcefully check for updates and tell the user that they must update before continuing to use the app.Does this help?Oct 5, 2011crocsnackSam:Thanks for your repsonse. We can implement your suggestion for Question 1, since when we create the SQL scripts we know what the new SQL schema version should be. However, with Question 2 we still have the following questions:a. How does the application know that the correct schema version should be? Our only thought would be to store it as an application or configuration setting, since we don't want to code it in the application. Is there another better way?b. Is there any way to just force the application to automatically run the update if the schema version is not up-to-date? Ideally at application startup we would want the update automatically execute and the restart the application.Oct 5, 2011a. How does the application know that the correct schema version should be? Our only thought would be to store it as an application or configuration setting, since we don't want to code it in the application.. About wyBuild, wyUpdate, the AutomaticUpdater. Overview of wyBuild: An overview of wyBuild including some of the more prominent features. Features in wyBuild: A summary of the most useful features in wyBuild. Changes in wyBuild wyUpdate : The complete list of changes to wyBuild and wyUpdate since the first publicly released version. wyBuild. wyBuild is the complete automatic updating patching solution. Included in the wyBuild installer is wyBuild (to design build updates), wyUpdate (the open source updater program), and the AutomaticUpdater. Download wyBuild (latest changes). Learn about wyBuild LimeLMwyBuild .1 (wybuild-setup.exe) Windows Download and Review
Your wyBuild is a great product and I love to see below features implemented in your future releases.1. add *.bat execute support after finishing updating (wybuild 1.2 only supports exe and com at the moment.)2. add force update option : e.g wyupdate.exe -f (bypass client.wyc and server version check)It's very helpful when my clients deleted some files accidentally or they're corrupted. He/she just needs to run wyupdate.exe -f to re-download all files from the server.Jan 16, 2009Your wyBuild is a great product and I love to see below features implemented in your future releases.1. add *.bat execute support after finishing updating (wybuild 1.2 only supports exe and com at the moment.)Good idea, it'll be in the next version.2. add force update option : e.g wyupdate.exe -f (bypass client.wyc and server version check)It's very helpful when my clients deleted some files accidentally or they're corrupted. He/she just needs to run wyupdate.exe -f to re-download all files from the server.Something very similar is already included in wyBuild 1.2. As it is now, when wyUpdate is patching your product, if it detects something wrong it downloads the full version of your product. Here's the option in the wyBuild project properties window:[attachment=0]wybuild-catch-all-updates.png[/attachment]Is this what you're suggesting, or are you talking about re-downloading an existing corrupt version?Jan 16, 2009for example: my software files are main.exe, data.dll, wyupdate.exe and client.wyc. If i run wyupdate.exe it will say my software is to date. if I delete main.exe and data.dll then run wyupdate.exe it still says my software is up to date. I just want wyupdate.exe to check for missing files and redownload them or just redownload them all when using something like wyupdate.exe -redownloadJan 16, 2009OK, now I get what you're saying. I have a couple more questions, though. How did the files get deleted in the first place?I need a more complete picture. Are these files anti-piracy things that pirates delete to get full access to your software?Jan 16, 2009The reason i want this feature to prevent my files from modifying by others. For example: i coded my main.exe to check for other files data.dll . *.dll CRC... if it detects those files are modified then it will run wyupdate.exe to redownload them. I believe the feature also helps other situations like customers deleted one or a few required files accidentally or web deployWeb Deploy: customers only need to download/run wyupdate.exe and it will download allwyBuild Download - Use wyBuild to make update patches and get
Getting StartedInstall wyBuildVideo TutorialStep-by-step walkthroughNew release workflowBasicsFAQ (Frequently asked questions)Executing filesRegistry changesDistribute wyUpdateTranslate wyUpdateSilently Check for UpdatesSilently update Windows ServicesRequirementsAutomatic UpdaterAutomaticUpdater introTutorial for Windows Forms appsTutorial for WPF appsTutorial for Windows ServicesAutomaticUpdater MembersTranslate the AutomaticUpdaterAboutChanges in 2.6.18AdvancedBuild from CommandlineEncrypting updatesCommands and VariablesCOM dll registering / unregisteringCustom wyUpdate VersionDownload sitesLimit or prevent updatesOffline updatesOverride the Server SiteProxies in wyUpdateServices (start / stop)Signing Updates in wyBuildVersion NumberswyUpdate CommandlineBuilding from CommandlineIn addition to the easy to use drag-and-drop interface, wyBuild offers a commandline interface to automate your update creation. With this commandline interface you can build your updates, add new versions using an XML file, build wyUpdate, and upload your updates.The wyBuild Commandline Builder is the "wybuild.cmd.exe" in the wyBuild installation folder. Here are the available commandline switches: Commandline switch Description /bu Build the updates & server files for your project. /bwu Build wyUpdate for the latest version of your app. /upload Upload the most recently built updates. -vs="" The start version - the version of your product that you're building from. If this switch is not present then the update is built from the oldest available version. -ve="" The end version - the version of your product that you're building to. If this switch is not present then the update is built to the newest available version. -add="" Add additional versions to your product using the XML specification below. -catchall="" If this "catchall" commandline argument is present you can override the setting for the "Create catch-all update for corrupt installations" option in your project's properties. Otherwise the value you have in your project is used. Return codesThe wyBuild Commandline Builder returns 0 on success and 1 on error.Building updatesBuilding updates from commandline is simply a matter of supplying the version ranges of the update you want to build:wybuild.cmd.exe "C:\YourProject.wyp" /buOr you can specify the version ranges you want to cover with the update:wybuild.cmd.exe "C:\YourProject.wyp" /bu -vs="1.0" -ve="1.1"Adding new versionsYou can add new versions to your wyBuild project by using either the "/bu" or "/bwu" commandline switch along with the "-add" switch. For example:wybuild.cmd.exe "C:\YourProject.wyp" /bu -vs="1.0" -ve="1.2" -add="newversions.xml"This adds the new version using the xml specification (see below) while also building the updates for your product in the range from v1.0 to v1.2.New Versions XML FormatThe format of the XML file required to add new versions by commandline is rather simple. Below is an example: 1.2 Some very very cool stuff NewName.dll Adding filesTo add files and folders there are 2 elements that you need to use: and . The element defines the destination folder and contains all and elements: ... ... ...You can also specify destination subfolder by nesting elements: ... ... If you want to add a file to wyBuild, but want to use a filename different from the source filename, then use the following element format:New filename.exeAvailable destination directoriesThe blocks (...) have a dir attribute which corresponds to destination directory: Directory Abbreviation Destination basedir The directory where your program is installed (e.g. C:\Program Files\YourProgram) commdesktop The common desktop. cudesktopWalkthrough for wyBuild, wyUpdate, and the
The current user's desktop. commstartmenu The common start menu. custartmenu The current user's start menu. commappdata The common application data directory. currappdata The current user's roaming application data directory (e.g. C:\Users\User Name\AppData\Roaming) currlocalappdata The current user's local application data directory (e.g. C:\Users\User Name\AppData\Local) commonfilesx86 The Common Files directory for 32-bit %ProgramFiles%\Common Files on 32-bit Windows %ProgramFiles(x86)%\Common Files on 64-bit Windows commonfilesx64 The Common Files directory for 64-bit %ProgramFiles%\Common Files on 64-bit Windows The update will fail to install on 32-bit Windows sys32 The system32 directory for 32-bit C:\Windows\System32 on 32-bit Windows C:\Windows\SysWOW64 on 64-bit Windows sys32x64 The system32 directory for 64-bit C:\Windows\System32 on 64-bit Windows The update will fail to install on 32-bit Windows root The root Windows drive (e.g. C:\) temp The temporary directory. Adding a folder and its contentsTo recursively add a folder along with all files and folders within it simply use the element. For instance, to add the folder "C:\Folder to add" along with all of its contents add the following Folder element:... ......Let's say you want to add all the files and folders within a particular folder, but not the folder itself. You can do this by adding the insideonly="true" attribute:... insideonly="true" /> ......Adding shortcutsTo add a shortcut simply use the element. Here's an example shortcut named "Your Awesome App.lnk" that will be added to the desktop that references the "Your App.exe" file in the "Your program's folder" directory:... Your Awesome App.lnk ...... Shortcut Attribute Description source The location the file you're making the shortcut to. Use the %basedir% variable to reference files in the "Your program's folder" in wyBuild. That is, wherever wyUpdate.exe is sitting on your user's computer. startin The start path (or current directory) of the shortcut.If this attribute is absent the default value is the path of the "source" attribute. run The "run" attribute lets you set how the executable is started. It can have one of 3 possible values: normal minimized maximized If this attribute is absent the default value is normal. comment The comment string of the shortcut. This is the tooltip text the user sees when they hover their mouse over the shortcut. Removing & overwriting existing versionsYou can also remove and overwrite existing versions in your wyBuild project file. To overwrite an existing version (if it exists), add the overwrite="true" attribute to the element: 1.2 ... You can also explicitly remove versions: 1.2 ... If you would like wyBuild to show an error if you try to remove a version that doesn't exist then use the hardfail="true" attribute:Executing filesAs shown in the "Executing files in your update" article you can execute *.exe, *.bat, *.cmd, and *.msi files either before or after you've installed your update. File Attribute Description elevation The "elevation" attribute lets you set the elevation level of the executable to be started. It can have one of 3 possible values: same: Start the executable the same elevation level as wyUpdate. not: Start as a non-elevated process (the same elevation level as the Windows Shell). elevated:. About wyBuild, wyUpdate, the AutomaticUpdater. Overview of wyBuild: An overview of wyBuild including some of the more prominent features. Features in wyBuild: A summary of the most useful features in wyBuild. Changes in wyBuild wyUpdate : The complete list of changes to wyBuild and wyUpdate since the first publicly released version.Comments
이 페이지에서는 .wyc 파일 확장자에 대해 자세히 살펴 보겠습니다..wyc 파일 형식이 정확히 무엇이며 어떻게 사용할 수 있는지 설명해 드리겠습니다. 이러한 유형의 파일에 대해 더 자세히 알고 싶다면 해당 파일을 찾을 수 있는 위치를 알려드리겠습니다. 또한 .wyc 파일을 다른 형식으로 변환해야 하는 경우 변환 방법에 대한 몇 가지 팁도 알려드립니다.이 파일 확장자와 관련된 2개의 파일 형식을 살펴봅시다!콘텐츠wyBuild Version DatawyUpdate Compressed Client Data저희 웹사이트가 여러분에게 유용한 정보를 제공할 것이라 믿습니다. 궁금한 점이 있으면 언제든지 문의하세요!wyBuild Version DataThe WYC file belongs to the Data category and works with wyBuild, being used as a wyBuild Version Data. wyBuild is a utility that gives developers the ability to create software update patches and distribute them to their user base quickly and easily. The developer is still actively supporting the wyBuild, likely. Our data shows that wyBuild uses 3 more file types.프로그램 이름: -마임 유형: application/octet-stream별칭:-관련 확장 프로그램:.iuc wyUpdate Client Data.udt wyUpdate Update Details FilewyUpdate Compressed Client DataThe WYC file belongs to the Data category and works with wyUpdate, being used as a wyUpdate Compressed Client Data. wyUpdate is the open source updater that's included with wyBuild. wyUpdate checks for updates, downloads any that are available, and safely updates your program. The developer is still actively supporting the wyUpdate, likely. Our data shows that wyUpdate uses 2 more file types.프로그램 이름: -마임 유형: application/octet-stream별칭:-관련 확장 프로그램:.wyc wyBuild Version Data.wyp wyBuild Project.wyc 파일 확장자는 단일 유형의 파일에 속할 뿐만 아니라 이를 사용하는 다양한 종류가 있을 수 있습니다. .wyc 확장자를 가진 파일에는 다양한 콘텐츠 유형이 포함될 수 있습니다. 이 확장자에 대한 유용한 정보가 있으면 저희에게 알려주세요!.wyc 파일 확장자의 철자가 잘못되었을 수 있나요?데이터베이스에서 다음과 같은 유사한 확장자를 발견했습니다:.qyc Quantec Yardstick Plugin.dyc Xerox Printer Driver Configuration Data.wtc WaveThunder Configuration Data.wc WorldCraft Data.yc YAC Compressed.wyc 확장자는 자주 잘못 사용됩니다사람들은 때때로 .wyc 파일 이름 확장자를 혼동하는 경우가 있습니다. 지난 한 해 동안
2025-04-01With wyBuild you can deliver updates of your software to your users fast. No confusing interfaces - just simplicity.Make your users happy by keeping them up-to-date. They'll love having the latest bug-free versions of your software. They'll talk far and wide about how great your software is.Make your current users happy, attract more users, and make more money all with wyBuild.New Features:wyUpdate & wyBuild now support multiple languages. wyUpdate automatically detects the culture of the system, and selects the right language.Patching your files is now faster (especially for large files)Verifying downloads is now faster.Allow *.bat and *.cmd files to be executedAdd passive & active FTP transfer to the uploader.Add passive & active FTP transfer to the uploader.Increase the speed of the FTP uploader.wyUpdate now runs as a single instance (that is, only one instance of wyUpdate can update your product at once)Version comparison algorithm is now fasterNotable Bugfixes:Updated wyBuild to be easily understood by new users.Add proper support for unicode filenames and paths in updates.The file folder browser rejected unicode text when pasted in as a file or folder name.Languages that are only partially complete are now loaded correctly.Versions with "release candidate" are now parsed correctly.The menu items now look like system menus on Pre-VistaThe product key is now detected if it's entered in the installer.Cleaned up the administrator checking code - making it slightly faster.Increased the wyUpdate icon size in Windows 7 taskbar (so it no longer looks blocky)wyUpdate now gracefully handles corrupt self-update server files.Plus much more.Open SourceThe wyUpdate is open source (using the BSD license). Download the source and begin hacking away. It's C# 2.0 code.The wyBuild 14-day trial last for 14 non-consecutive days. That is, you can use wyBuild for once a month for the whole year and still have two trial days left. Or you can use it for 14-days in a row. It's your choice. This trial has no limitations and no popup-nags.If you need help, the wyBuild Help explains the harder to use features. Also, feel free to post any questions, suggestions, or bug-fixes. (No forum registration is required.)Here's a short video introduction to wyBuild ➡ Download wyBuild 1.3 now.Feb 28, 2009
2025-04-19Your wyBuild is a great product and I love to see below features implemented in your future releases.1. add *.bat execute support after finishing updating (wybuild 1.2 only supports exe and com at the moment.)2. add force update option : e.g wyupdate.exe -f (bypass client.wyc and server version check)It's very helpful when my clients deleted some files accidentally or they're corrupted. He/she just needs to run wyupdate.exe -f to re-download all files from the server.Jan 16, 2009Your wyBuild is a great product and I love to see below features implemented in your future releases.1. add *.bat execute support after finishing updating (wybuild 1.2 only supports exe and com at the moment.)Good idea, it'll be in the next version.2. add force update option : e.g wyupdate.exe -f (bypass client.wyc and server version check)It's very helpful when my clients deleted some files accidentally or they're corrupted. He/she just needs to run wyupdate.exe -f to re-download all files from the server.Something very similar is already included in wyBuild 1.2. As it is now, when wyUpdate is patching your product, if it detects something wrong it downloads the full version of your product. Here's the option in the wyBuild project properties window:[attachment=0]wybuild-catch-all-updates.png[/attachment]Is this what you're suggesting, or are you talking about re-downloading an existing corrupt version?Jan 16, 2009for example: my software files are main.exe, data.dll, wyupdate.exe and client.wyc. If i run wyupdate.exe it will say my software is to date. if I delete main.exe and data.dll then run wyupdate.exe it still says my software is up to date. I just want wyupdate.exe to check for missing files and redownload them or just redownload them all when using something like wyupdate.exe -redownloadJan 16, 2009OK, now I get what you're saying. I have a couple more questions, though. How did the files get deleted in the first place?I need a more complete picture. Are these files anti-piracy things that pirates delete to get full access to your software?Jan 16, 2009The reason i want this feature to prevent my files from modifying by others. For example: i coded my main.exe to check for other files data.dll . *.dll CRC... if it detects those files are modified then it will run wyupdate.exe to redownload them. I believe the feature also helps other situations like customers deleted one or a few required files accidentally or web deployWeb Deploy: customers only need to download/run wyupdate.exe and it will download all
2025-04-20Getting StartedInstall wyBuildVideo TutorialStep-by-step walkthroughNew release workflowBasicsFAQ (Frequently asked questions)Executing filesRegistry changesDistribute wyUpdateTranslate wyUpdateSilently Check for UpdatesSilently update Windows ServicesRequirementsAutomatic UpdaterAutomaticUpdater introTutorial for Windows Forms appsTutorial for WPF appsTutorial for Windows ServicesAutomaticUpdater MembersTranslate the AutomaticUpdaterAboutChanges in 2.6.18AdvancedBuild from CommandlineEncrypting updatesCommands and VariablesCOM dll registering / unregisteringCustom wyUpdate VersionDownload sitesLimit or prevent updatesOffline updatesOverride the Server SiteProxies in wyUpdateServices (start / stop)Signing Updates in wyBuildVersion NumberswyUpdate CommandlineBuilding from CommandlineIn addition to the easy to use drag-and-drop interface, wyBuild offers a commandline interface to automate your update creation. With this commandline interface you can build your updates, add new versions using an XML file, build wyUpdate, and upload your updates.The wyBuild Commandline Builder is the "wybuild.cmd.exe" in the wyBuild installation folder. Here are the available commandline switches: Commandline switch Description /bu Build the updates & server files for your project. /bwu Build wyUpdate for the latest version of your app. /upload Upload the most recently built updates. -vs="" The start version - the version of your product that you're building from. If this switch is not present then the update is built from the oldest available version. -ve="" The end version - the version of your product that you're building to. If this switch is not present then the update is built to the newest available version. -add="" Add additional versions to your product using the XML specification below. -catchall="" If this "catchall" commandline argument is present you can override the setting for the "Create catch-all update for corrupt installations" option in your project's properties. Otherwise the value you have in your project is used. Return codesThe wyBuild Commandline Builder returns 0 on success and 1 on error.Building updatesBuilding updates from commandline is simply a matter of supplying the version ranges of the update you want to build:wybuild.cmd.exe "C:\YourProject.wyp" /buOr you can specify the version ranges you want to cover with the update:wybuild.cmd.exe "C:\YourProject.wyp" /bu -vs="1.0" -ve="1.1"Adding new versionsYou can add new versions to your wyBuild project by using either the "/bu" or "/bwu" commandline switch along with the "-add" switch. For example:wybuild.cmd.exe "C:\YourProject.wyp" /bu -vs="1.0" -ve="1.2" -add="newversions.xml"This adds the new version using the xml specification (see below) while also building the updates for your product in the range from v1.0 to v1.2.New Versions XML FormatThe format of the XML file required to add new versions by commandline is rather simple. Below is an example: 1.2 Some very very cool stuff NewName.dll Adding filesTo add files and folders there are 2 elements that you need to use: and . The element defines the destination folder and contains all and elements: ... ... ...You can also specify destination subfolder by nesting elements: ... ... If you want to add a file to wyBuild, but want to use a filename different from the source filename, then use the following element format:New filename.exeAvailable destination directoriesThe blocks (...) have a dir attribute which corresponds to destination directory: Directory Abbreviation Destination basedir The directory where your program is installed (e.g. C:\Program Files\YourProgram) commdesktop The common desktop. cudesktop
2025-03-28.NET 2.0, 3.0, and 3.5 appsIf your app is compiled for .NET 2.0, 3.0, or 3.5 then use AutomaticUpdater.dll located in the "AutomaticUpdater" folder:C:\Program Files\wyBuild\AutomaticUpdater\AutomaticUpdater.dll orC:\Program Files (x86)\wyBuild\AutomaticUpdater\AutomaticUpdater.dllFor .NET 4.x appsIf your app is compiled for .NET 4.x then use AutomaticUpdater.dll located in the "AutomaticUpdater\Microsoft .NET 4.0" folder:C:\Program Files\wyBuild\AutomaticUpdater\Microsoft .NET 4.0\AutomaticUpdater.dll orC:\Program Files (x86)\wyBuild\AutomaticUpdater\Microsoft .NET 4.0\AutomaticUpdater.dllStep 2: Using the AutomaticUpdaterBackend classThe AutomaticUpdaterBackend class contains all the functionality to add automatic updating to your service or console app. The way to use the AutomaticUpdaterBackend differs between Windows Services and Console Apps, so we've split it into 2 separate examples:For Windows ServicesIf you're using the AutomaticUpdater with a Windows Service, the first thing you need to do is make sure your service will be installed as a "LocalSystem" service. Please note that a "LocalSystem" service is different than a "LocalService" service: A "LocalSystem" service is equivalent to an admin account; the AutomaticUpdater will be able to install completely silently. A "LocalService" service is equivalent to a limited user account; the AutomaticUpdater will fail to install your updates.Create and instance of the AutomaticUpdaterBackend class in the OnStart() method of your service:using wyDay.Controls;static AutomaticUpdaterBackend auBackend;protected override void OnStart(string[] args){ auBackend = new AutomaticUpdaterBackend { //TODO: set a unique string. // For instance, "appname-companyname" GUID = "a-string-that-uniquely-IDs-your-service", // With UpdateType set to Automatic, you're still in // charge of checking for updates, but the // AutomaticUpdaterBackend continues with the // downloading and extracting automatically. UpdateType = UpdateType.Automatic, // We set the service name that will be used by wyUpdate // to restart this service on update success or failure. ServiceName = this.ServiceName }; auBackend.ReadyToBeInstalled += auBackend_ReadyToBeInstalled; auBackend.UpdateSuccessful += auBackend_UpdateSuccessful; //TODO: use the failed events for logging & error reporting: // CheckingFailed, DownloadingFailed, ExtractingFailed, UpdateFailed // Initialize() and AppLoaded() must be called after events have been
2025-04-17Getting StartedInstall wyBuildVideo TutorialStep-by-step walkthroughNew release workflowBasicsFAQ (Frequently asked questions)Executing filesRegistry changesDistribute wyUpdateTranslate wyUpdateSilently Check for UpdatesSilently update Windows ServicesRequirementsAutomatic UpdaterAutomaticUpdater introTutorial for Windows Forms appsTutorial for WPF appsTutorial for Windows ServicesAutomaticUpdater MembersTranslate the AutomaticUpdaterAboutChanges in 2.6.18AdvancedBuild from CommandlineEncrypting updatesCommands and VariablesCOM dll registering / unregisteringCustom wyUpdate VersionDownload sitesLimit or prevent updatesOffline updatesOverride the Server SiteProxies in wyUpdateServices (start / stop)Signing Updates in wyBuildVersion NumberswyUpdate CommandlineThis article will teach you how to use the AutomaticUpdater in apps without a UI such as Windows Services and console apps. If you're making an app with a graphical user interface, then see one of the following articles: Windows Forms article Windows Presentation Framework (WPF) articleIf you're making a GUI app that happens to have Windows Services that you'd like to update, then you can just use the GUI version of the AutomaticUpdater and Start and Stop Windows Services as part of your update.First, get wyBuildYou need wyBuild to use the AutomaticUpdater, so download wyBuild now. You can use it free for 21-days with no restrictions. And if you don't like it you can uninstall it - no hard feelings & no files laying around.Then, work yourself through steps 1-3 of the step-by-step walkthrough. This will teach you how to make update patches. Once you've read the walkthrough you're ready to add the AutomaticUpdater to your app:Step 1: Add "AutomaticUpdater.dll" reference to your appThe first thing you need to do is add the AutomaticUpdater.dll reference to your app. You can do this by right clicking the "References" folder in Visual Studio, clicking "Add Reference...", then choosing the "Browse" tab in the "Add references" dialog:Then simply choose the correct AutomaticUpdater.dll for your app. There are 2 separate builds of the AutomaticUpdater: one for .NET 2.0, 3.0, and 3.5 apps and one for .NET 4.x apps.For
2025-04-13