You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: load interop dlls for iom/com, supply appname (#1409)
**Summary**
This change updates both IOM & COM connections to load SAS interop dlls so that we can specify an application name when starting a connection. We attempt to load the DLLs in the following order...
- A user specified location (specified in a new profile option, `interopLibraryFolderPath`). If this location can't be found, we proceed checking other locations
- If no `interopLibraryFolderPath` is specified, we attempt to lookup the path in the registry
- Then, in the Integration Technologies folder
If all of these fail, we provide the user with an error message.
**Testing**
- [x] Tested each different way of loading interop dlls, and made sure connections worked as expected
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). If you introduce breaking changes, please group them together in the "Changed" section using the **BREAKING:** prefix.
6
6
7
+
## [Unreleased]
8
+
9
+
### Added
10
+
11
+
- Add application name to ITC-based (IOM/COM) connections ([#762](https://github.com/sassoftware/vscode-sas-extension/issues/762))
Copy file name to clipboardExpand all lines: website/docs/Configurations/Profiles/additional.md
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,3 +132,43 @@ For SAS Viya connection profiles, you can set up autoexec code that executes eac
132
132
}
133
133
}
134
134
```
135
+
136
+
## SAS Interop Library Settings
137
+
138
+
SAS Interop library settings can be configured for ITC-based connections ("remote - IOM" and "local" connection types). ITC-based connections have a dependency on `SASInterop.dll` and `SASOManInterop.dll`. The extension tries to load these libraries from the following locations (ordered by priority):
139
+
140
+
1. The path specified in `interopLibraryFolderPath`. This should be an absolute path to the folder containing the files listed above.
141
+
2. If `interopLibraryFolderPath` is empty or invalid, the extension will attempt to resolve the path from Windows registry
142
+
3. If steps 1 and 2 fail, the extension will attempt to load libraries from the default Integration Technologies Client folder (`C:\Program Files\SASHome\x86\Integration Technologies`)
143
+
144
+
The following demonstrates how to setup `interopLibraryFolderPath` in user settings:
|`host`| IOM Server Host | Appears when hovering over the status bar. |
28
+
|`username`| IOM Server Username | The username to establish the IOM connection to the server. |
29
+
|`port`| IOM Server Port | The port of the IOM server. Default value is 8591. |
30
+
|`interopLibraryFolderPath`| IOM interop library path | A custom path to a folder containing SAS interop libraries (`SASInterop.dll` and `SASOManInterop.dll`) |
|`host`| Indicates SAS 9.4 local instance | Defaults to "localhost" for com |
22
+
|`interopLibraryFolderPath`| COM interop library path | A custom path to a folder containing SAS interop libraries (`SASInterop.dll` and `SASOManInterop.dll`) |
0 commit comments