It is exciting to see the new functionalities, Branch & Merge, are now available in SourceAnywhere 6.0. You can quickly find them on toolbar, or by right-clicking any folder.
In this tutorial, let’s go through how to use Branch and Merge step by step.
Download 30-day free trial
How to Create/Remove Branches
Create a branch:
- In the Source Control explorer, select a folder or file as the source.
- Click Branch.
- Select a version and specify the target branch.
- Successfully branched.
Remove a branch:
- Select a branch and click Delete.
- When you click OK, the branch folder will be removed from the project tree.
Note: this does not mean the branch has been completely removed. If you create a new branch which has the same name to previous one, you will see the error message displayed in console: Deleting item $/test-branch: A deleted item with the same name test-branch exists already. Rollback transaction.
- To completely remove the branch from your source code repository, right-click the parent folder, and select Properties. Then purge the deleted branch.
How to Merge Files
- Select a branch from the Project Tree, and click Merge.
- Specify the target version and click Next.
- Next, you can see the list of changed files. Right-click the file to resolve the conflict.
- Click Resolve, and select Auto Merge (just choose the option you like).
- Finally, check in all merged files.
How can I merge folders quickly and reliably?
In order to merge items quickly and reliably, we suggest:
- Ensure Target Branch has no checked out or pinned items. If items in the target branch are checked out or pinned, they will fail to be updated. Please check in all items, or undo all outstanding check outs, before merging. Also, make sure all pinned items are unpinned before attempting a merge.
- Make sure the file you want to merge is mergeable. In SourceAnywhere, there are two file types: Mergeable and Binary. You can find out or change the type of a file via File Properties -> General Tab -> Type. SourceAnywhere cannot merge binary files. If the file you want to merge is binary, you’ll need convert it to a mergeable file before you can merge it.
If you want to convert files in bulk, we suggest using our File Type Convert Tool.
SourceAnywhere Online Manual
We’re more than excited to announce that Dynamic .NET TWAIN 5.3 is released. There are some new improvements we’d like to share with you.
- A new property called ScanInNewProcess
you can set this property to true to enable the feature of acquiring images in an independent process. With this feature, you can now access 32-bit TWAIN scanners from 64-bit applications.
- Other minor fixes and tweaks
To learn full features or try out the latest version, please visit at
If you have a valid software maintenance contract, or are using version 5, please contact firstname.lastname@example.org for FREE upgrade to this new version.
If you are ready to purchase a license, please visit our Online Store or send your order to email@example.com.
For any tech questions, please email firstname.lastname@example.org.
Dynamsoft contributed an article to THE BarCode News that ran July 13, 2014. Start reading it below.
The use of barcodes in healthcare markets has been advocated going back to the 1970s. The Healthcare Information and Management Systems Society (HIMSS) has emphasized a high priority on using barcode technology to reduce medical errors for better patient safety. The technology has helped solve many human errors. For example, the US Department of Health and Human Services has stated the use of barcodes has reduced medication error rates by as much as 85 percent. To those in the barcode industry, it is well known that the technology helps improve workflow and efficiency. This is true across a myriad of industries, but in the medical field it can also help save lives. So, what do technical staff need to consider to ensure a successful implementation of barcode technology in their healthcare practice?
This article will detail five tips for implementing barcodes in medical records management applications. This includes managing documents such as order requisitions, test results, and patient charts / medical records. The tips will cover technical and workflow considerations.
Really understand the software platform
Learn the detailed platform requirements of the Electronic Health Records (EHR) system you use or plan to use. This includes any desktop, web or mobile application, or combination of any of these. For an example, let’s look at a potential platform requirement for a web-based application. If it’s web-based, you’ll want to identify what browser types the application needs to support. This includes determining if users will be required to maintain a minimum browser type or version. For example, will your web-based application work only on IE version 9 or later? Or, is it important that you support other browsers too: Chrome, Firefox, Safari, Opera, and so on? Ensuring support for browsers will help guarantee continuous workflow and reduce support issues. Once you understand this requirement you can proceed with a corresponding barcode application programming interface (API) to save you development time. There are some open source barcode libraries available. A popular one is ZXing, also known as “Zebra Crossing”). You might instead opt for a third party barcode software development kit (SDK). Commercial SDKs typically provide better barcode processing results, wider barcode type support, and better customer service. Obviously they can also save on development time and costs versus researching, understanding, identifying, creating and supporting an API you built in-house.