TDL Byte #11: Quick and easy code migration to higher release!

Discussion in 'Tally & TDL Learning HUB' started by admin, Nov 7, 2015.

  1. admin

    admin Administrator Staff Member

    TDLByte #11
    Dear Developers,
    In our previous TDLByte #10 we had introduced you to 'Version Compatibility Check' in
    Tally.Developer 9 Release 5.0
    . We explained that how this feature can assist you in migrating your code to higher product releases in just a matter of few minutes. Also, we outlined the steps to be followed in order to migrate the code.
    Today, we will explain these steps in detail:
    Step 1
    Load Default TDL Code of Base Release

    Base Release: Tally.ERP 9 Release up to which the customization is compatible with. For example let us consider release 4.8 as
    base release.
    [Read more...]
    Step 2
    Generate Compatibility Metadata

    This is a step where a tdlserver.ddif file is created in the
    Tally.ERP 9 folder.
    This file contains the information about the TDL definitions in the source code of the selected release.
    (DDIF – Developer Description Index File).
    [Read more...]
    Step 3
    Load Default TDL code of Target Release

    Target Release: Tally.ERP 9 Release to which the customization has to be migrated to. For example let us consider Release 5.0 as target release.
    [Read more...]
    Step 4
    Load Customization Project and Perform Version Compatibility Check

    [Read more...]
    Step 5
    Analyze results and make changes

    Once the Version Compatibility Check is performed, the results of the same is displayed in the Build tab of the Output window. It display errors, warnings and remarks, with reference and description about them.
    [Read more...]
    Now just analyze the results and make the necessary changes, to make your project compatible with Release 5.0!
    How did this magic happen?

    Let us see what the system does, when version Compatibility Check is performed:
    Now that you are aware of the steps involved, our next TDLByte will give you more insight on errors and warnings. Until then, try migrating your project using this powerful tool.
    Stay tuned!

Share This Page