如何通过编程方式配置LabVIEW与TortoiseSVN的比较选项？

Got it, let's walk through how to automate that LabVIEW Compare + TortoiseSVN setup you've already done manually—perfect for deploying to other users' machines without having them click through all the steps. Here's a practical, LabVIEW-focused approach:

1. First, Map the Manual Setup to Configurable Targets #

Before coding, let's recap the key settings you configured manually—these are the spots we'll automate updating:

LabVIEW Side (Registry) #

All external compare tool settings live in the Windows user registry:

• Path: HKEY_CURRENT_USER\Software\National Instruments\LabVIEW\<LabVIEW Version>\Compare
• Key values to set:
  • UseExternalCompareTool: DWORD value 1 (enables external compare)
  • ExternalCompareToolPath: Full string path to TortoiseMerge.exe (default: C:\Program Files\TortoiseSVN\bin\TortoiseMerge.exe)
  • ExternalCompareToolArguments: String with command-line parameters LabVIEW uses to pass VIs to TortoiseMerge. A working format is /base:"%1" /mine:"%2" (matches TortoiseMerge's two-file comparison input)

TortoiseSVN Side (2 Options) #

Configure TortoiseSVN to use LabVIEW for .vi file comparisons:

• Option 1: Registry
  • Path: HKEY_CURRENT_USER\Software\TortoiseSVN\ExternalDiff
  • Add a string value for .vi with: "C:\Program Files\National Instruments\LabVIEW\<LabVIEW Version>\LabVIEW.exe" "%base" "%mine" -compare"
• Option 2: TortoiseSVN Config File
  • File location: %APPDATA%\TortoiseSVN\config
  • Edit the [external] section to add:

    *.vi="C:\Program Files\National Instruments\LabVIEW\<LabVIEW Version>\LabVIEW.exe" "%base" "%mine" -compare
    

2. LabVIEW Code to Automate the Setup #

Use LabVIEW's built-in registry and file I/O functions to modify these settings dynamically:

Part A: Configure LabVIEW's External Compare Tool #

1. Use the Registry Set Value function (from Programming > File I/O > Registry palette)
2. Dynamically get the current LabVIEW version with the Get LabVIEW Version function (or hardcode it if deploying to a specific version)
3. Build the full registry path (e.g., HKEY_CURRENT_USER\Software\National Instruments\LabVIEW\2023\Compare)
4. Set each required key value as outlined above—make sure to use the correct data type (DWORD for the enable flag, string for paths/arguments)

Part B: Configure TortoiseSVN for VI Comparison #

Choose either method based on your preference:

• Registry Method: Use Registry Set Value to add the .vi association under the TortoiseSVN ExternalDiff path
• Config File Method:
  1. Use File Read to load the TortoiseSVN config file
  2. Check if the [external] section exists; if not, append it to the file
  3. Add the .vi association line, ensuring you handle quote escaping correctly in LabVIEW strings
  4. Write the modified content back to the config file

3. Deployment Best Practices #

• Prerequisite Checks: Add logic to verify:
  • The target machine has the correct LabVIEW version installed (match the path in your code)
  • TortoiseSVN is installed (validate the TortoiseMerge.exe path exists, or let users input a custom path if needed)
• User Permissions: All settings are in HKEY_CURRENT_USER or user-specific app data, so no admin rights are required
• Testing: Validate the setup on a clean machine—confirm LabVIEW launches TortoiseMerge when comparing VIs, and TortoiseSVN uses LabVIEW for .vi diffs

内容的提问来源于stack exchange，提问作者Nivedhitha