- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- 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
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Extension for Silverlight
The first step is to uninstall any previous Silverlight Runtime you may have and install Silverlight Developer Runtime version 5.1.50918.0.
To automate windowless Silverlight applications you need to activate the UiPath Extension for Silverlight. The simplest way to install the bridge extension is by opening Studio, navigating to Tools > UiPath Extensions, and selecting Silverlight > Install.
You can also install the UiPath Extension for Silverlight by using a command prompt opened with administrator rights, and running one of the following commands:
C:\Program Files\UiPath Studio\v8\UiPath\SetupExtensions.exe /silverlightC:\Program Files\UiPath Studio\v8\UiPath\slinject.exe /install- This command displays more info in the console.C:\Program Files\UiPath Studio\v8\UiPath\slinject.exe /uninstall- This command uninstalls the extension. This also removes any extension entries in the Control Panel Add/Remove Programs section.
SetupExtensions.exe might fail silently (at least in older versions of Studio).
Windows auto-update can silently update the Silverlight runtime. It is recommended to clear the Enable Microsoft Update option in the last step of the Silverlight installer wizard or configure Silverlight updates using:
C:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\Silverlight.Configuration.exe
You can check the windowless parameter using the UiExplorer tool as follows:
- Search for the
<param name=”windowless” />tag under the corresponding<object />element. - Use the DOM Explorer in Internet Explorer (press F12 to open it).
Silverlight browser applications can be opened only in Internet Explorer because all the other major browsers discontinued NPAPI - an API used by the Silverlight browser plugin. There are also standalone Silverlight applications that can be used outside of the browser.
A major Windows update, which changes the Windows version to 20H2 can break Silverlight interactions. To fix this issue, you must:
- Uninstall Silverlight Developer Runtime and the UiPath Extension for Silverlight.
- Install Silverlight Developer Runtime version 5.1.50918.0.
- Install the UiPath Extension for Silverlight.
<object> HTML tag which can specify a windowless parameter. If the Silverlight target app has the parameter windowless=false (which is the default) then there is no need to activate the UiPath Extension for Silverlight because Active Accessibility and UIA are already available. This also applies to out-of-browser Silverlight applications.
You can check the windowless parameter as follows:
- For Internet Explorer Silverlight applications - Use the DOM Explorer in Internet Explorer to search for the
<param name=”windowless” />tag under the corresponding<object />element. -
For out-of-browser Silverlight applications - Use UIExplorer to search for the
<param name=”windowless” />tag under the corresponding<object />element.Note: Silverlight automation only works with the Developer Runtime version installed.
If you’re having problems automating with the extension for Silverlight it is recommended to try the following:
-
Make sure you have Silverlight Developer Runtime and not the regular non-developer version. You have the developer runtime if one of the following files are present:
C:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\agcore.debug.dllC:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\dbgshim.dll
-
Check the Silverlight runtime version. The version needs to be 5.1.50918.0 and you can find it at the following locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight(64bit) - in the Windows Registry Editor;HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Silverlight(32bit) - in the Windows Registry Editor;- The Settings > Apps & features window;
- The Details tab of the Silverlight installer file Properties.
- Go to the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Deskover\UiPathand look for the SLInstalled value, which is used by UiPath to keep track of the installation. If the value is 0, then the extension for Silverlight is disabled. -
Check if the
slinject.exe /installcommand created the required config file:C:\Program Files (x86)\Microsoft Silverlight\5.1.50918.0\System.Windows.ini. It needs to contain the following settings:GenerateTrackingInfo=1andAllowOptimize=0 -
At least one instance of the
sllauncher.exe /overwrite /emulate:"SLBroker.xap" /origin:"https://www.uipath.com/SLBroker.xap"process needs to exist at Silverlight apps automation startups. You can find the process using the Process Explorer tool. - If any of the previous steps did not pass automatically when installing the extension, you can try to complete them manually.
-
Collect traces while trying to select controls inside the Silverlight app as explained on this link. For regular ETL traces you can also set the
UIPATH_SLHOOK_CONSOLE_LOGGINGenvironment variable to 1 or true (case insensitive). This enables log messages and other debugging info in the browser console window (F12 to open). These messages are generated by the target Silverlight application and they are logged only in the browser console because of technical and performance limitations.Note: You have to set the environment variable before performing any UI automation. Make sure to restart UiPath and the Silverlight target application.
