The root object of the Merge automation library is the Application object. Use #include if you prefer to use ATL or hand-crafted COM client code. Imports type definitions into the global namespace. ![]() Use #import if you prefer to use Visual C++’s Compiler COM Support (CCS) model. Imports type definitions into the namespace Merge70. Both files can be found in in the Merge installation folder, typically C:\Program Files\Araxis\Araxis Merge. You can reference either the pre-compiled type library ( Merge.tlb) file or IDL-generated header file ( Merge.h) that ships with Merge. Once the reference has been added, the Merge automation objects and types are found in the Merge70 namespace. To use the Merge Automation API in Visual Studio.NET 2005 managed projects, you can either Add a reference to the pre-built COM interop assemblies ( ) included in the Merge installation folder, or you can add a reference to the Merge Type Library as follows: Scripting languages (VBScript and JScript for example) typically use late-binding, so this step is not required. Referencing the Automation APIįor client languages that use early-binding (or stongly-typed) access to the API’s COM objects, you will need to add a reference to the Automation API to your project. In summary, deployment as a server component requires the purchase of two Merge licences rather than the one required for normal desktop use, though you are referred to the full EULA for the definitive terms. The End-User Licence Agreement for Araxis Merge Software has specific provision for both desktop use and for Merge to be deployed as a component of a server application that provides services to multiple users. If you require assistance with using the Automation API or developing a plugin file system, please feel free to contact Araxis. The FolderComparisonPerforceChangeListReport.js example shows how this may be done for Perforce. Thus, for example, you can use Automation to create a report of the changes in your SCM system between two dates, branches or revisions. Remember that Merge offers direct access to various SCM repositories via its Virtual File System (VFS) Plugins. ![]() ![]() The C++ source code to a number of the command-line utilities (such as compare.exe) included with Merge is also provided. The examples are in a variety of languages – mostly JScript and CSharp, but also VBScript and Visual Basic. ![]() Many of these perform valuable tasks others will give you ideas for how you could use Merge to provide solutions for your own environment. The AutomationSamples directory within the Merge installation directory contains a wealth of complete Automation API programming examples. Automation API example scripts and programs The API’s event model supports the connection point, native interface, and Windows Scripting Host ConnectObject models. The API supports both early-binding and late-binding (via IDispatch), and can therefore be used by a majority of Windows Automation clients. NET assembly rather than the Automation API. NET-capable language and you do not need to present the Merge user interface to the user, you may wish to use the Merge. Using Automation, you can tightly integrate Merge with other applications, or make it part of your workflow. The Merge Automation API enables you to control it from JScript, Visual Basic (including VBScript), C#, C++, and many other programming languages and environments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |