Adding File System.dll back to TestShell after and upgrade. #37
Quali-Community
started this conversation in
Useful Tips & Guides
Replies: 1 comment
-
Thanks for sharing John Koenig. Few comments: 1. If you upgrade from a previous version, the library will still be there. 2. If you install a new environment, then you will not have it (but probably won't have tests to make sure are working with the library). Anyway, no need rename the file itself before loading it, you can rename the library itself in Studio and it will affect the way it's displayed in the tools library and tests. Yaniv Kalsky (Yaniv.K) - 11/16/2020 05:42 PM |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If you are using the "File System.dll" library in your tests and you are planning to upgrade a pre 9.1GA CloudShell to a newer version, you will need to manually download and re-install this library. Quali removed File System.dll starting with version 9.1GA, it is still supported and documented just no longer included in the CloudShell Suite.
Here's where to find it:
https://support.quali.com/
Click Quali's Download Center
Click Quick navigation links: Automation Tools and Libraries
Click Download Automation Tools and Libraries
Click API Libraries
Scroll to the very bottom of the page
Click FileSystem Library 5.2.0.6
To match the naming convention of your current tests I recommend renaming the .dll before importing into TestShell. The .dll was previously named "File System" with a space between File and System.
Extract the .zip file
Copy to your libraries folder
Rename "QualiSystems.Libraries.FileSystem.dll" to "File System.dll" or whatever your test environment calls it.
Run TestShell Studio as Administrator
Go to the Libraries Tool under Admin
Right-Click on the Libraries folder and select New
Add the File System.dll
Refresh the Library Tree
Right Click on File System.dll and Click Check-in
Load a test that uses the File System Library and verify function. If you find your File System.dll has a different name, you can go back to libraries and rename the library to a name that matches your environment. Just remember to check it back in if you make any changes.
John Koenig (John.Koenig18) - 11/10/2020 01:12 PM
· 5283 ·
Beta Was this translation helpful? Give feedback.
All reactions