- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- About Version Control
- Managing Projects With GIT
- Managing Projects With TFS
- Managing Projects With SVN
- Workflow Diff
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Managing Projects With SVN
-
In the Team tab, select Open from SVN. The Open from SVN Repository window opens.
-
Type in the Repository URL or use the
button to open the repository browser.
In the repository browser, you can browse to and select an existing folder or copy the Selected Path. Click OK to confirm the selection and close the window.
- Pick an empty Check out directory. Select the Use credentials box and fill in your Username and Password. Click Open. The project is now available in the check out directory.
-
When you open a file from Studio, for example,
Main.xaml, a Question dialog box opens with two options for pulling the file from the repository:- Check out latest and edit - opens the latest version of the
Main.xamlfile from the repository, in edit mode. The Break Lock option allows you to check out a project from a SVN repository that was previously checked out by a different user. -
Open local as read only - opens the local version of the
Main.xamlfile in read-only mode. The Package Manager can be opened even if the files are in read-only mode, but in order to perform changes and install dependencies, theproject.jsonfile needs to be checked out.Selecting the checkbox for Always checkout latest and edit and don't show me this again, and then the Check out latest and edit option propagates your choice for future occurrences. Regardless of your choice, theproject.jsonfile still needs to be checked out separately for certain changes to take effect.
- Check out latest and edit - opens the latest version of the
- Create or open a project in Studio from the Start tab in the Backstage view. Click Start > Team > Add to TFS button, or Add to Source Control > Add to SVN shortcut in the status bar. The Add to SVN window is displayed.
-
Type in the Repository URL or use the
button to open the repository browser.
In the repository browser, you can browse to and select an existing folder, or click Create Folder
above the left navigation pane to add a new folder. Click OK to confirm the selection and close the window.
- If applicable, select Use credentials and type in the User and Password. Click Add to upload the project to the SVN repository.
-
In the Check In Changes window, select the files that you would like to add to the repository and write a Commit Message.
- Click Check In. The files are now available in the repository, together with the Commit message. The
project.jsonfile returns to read-only mode in Studio.
When a project is added to SVN, the context menu in the Project panel includes SVN-specific options. For more information, see Context Menu Options for SVN and TFS.
- Connect one of your projects to your SVN repository.
-
Right-click the
.xamlfile and select Check Out for Edit. The latest version of the.xamlfile is mapped locally and opened in the Project panel. It becomes locked for editing until it’s checked in. Perform any sort of changes to the files.Note: Once a file is checked out from the SVN repository, it is no longer available for check out by other users with access permissions. - Right-click the
.xamlfile or project node, and select Check In, or click the
icon in the Status bar, which also counts the number of uncommitted changes. The Check In Changes window is displayed.
-
Review the changes and check the Show Unversioned Files box to add imported files to the repository. Write a Commit Message to describe the changes.
- Click Check In. The latest version is now available in the repository, together with the Commit message. In Studio, the
project.jsonfile returns to the read-only mode. -
Click Start > Team > Disconnect to disconnect the current project from source control.
Note: If you edit a file from a project added to source control in an external editor, the change is visible in the Project panel and the status bar only after you click Refresh
in the Project panel.
If you work on a shared machine, you might need to change credentials to the current SVN repository before committing any changes to your project.
Go to Start > Team tab and select Change Credentials from the SVN section. Input your username and password for the current repository and select OK.
