If you add a coded step in the Standalone version and use logic contained in an outside assembly, you will need to add a reference to that assembly. Just like Visual Studio, project references in the Standalone version are project specific. Adding an assembly reference in one project does not make it available to other projects.
Open or create a test project in the Standalone version and open the Project Settings.
Select the Script section in the Settings dialog. You can see a list of all referenced dlls.
Click Add Reference to browse your computer for an assembly in dll form.
Locate the assembly and click Open. The new dll will appear in your Project References list. Compile the project to check for any errors related to the added assembly file.
Note! You must add using or Imports statements in the test code-behind file in order to directly use the custom dll in the coded step.
Note! Test Studio will not find references to a dll in the default sub-folders of the project folder. These include: bin, Properties, obj, Data, Backup, TestResults, Results, TestLists, and Profiler Configurations. If you attempt to add a reference to a custom dll in these locations, the following two errors patterns will appear in your application log when you run your test:
[09/03 10:53:15,Telerik.TestStudio.RemoteExecutor.exe(15300:14),ProjectModel] Project.Compile() : Unable to add reference Project2012SP2\Profiler Configurations\ClassLibrary5.dll. Exception: System.IO.FileLoadException: The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
[09/03 10:53:15,Telerik.TestStudio.RemoteExecutor.exe(15300:14),Execution] TestPlatform.OnRunnerError() : Error during remote runner execution: Compile failed: c:\Users\yee\AppData\Local\Temp\1\Projects\ce1cb993-aea7-46e9-9aa1-5d0493ddf4fc\Project2012SP2\Assembly.tstest.cs(18,7) : error CS0246: The type or namespace name 'ClassLibrary5' could not be found (are you missing a using directive or an assembly reference?)