01-27-2023 03:42 AM - edited 01-27-2023 03:44 AM
While creating an ASAM XIL object reference for initialization of ETAS EE. I am getting an error in Teststand 2017 x64, whereas I have run this step previously while it was running smoothly but after unloading all modules, I am getting this error even after killing the processes and restarting the restarting the machine I am unable to execute this step and unable to create object reference. Just wanted to know if there is any issue with .Net or file access permissions.
.
An exception occurred inside the call to .NET member 'ValueFactory':
System.IO.FileNotFoundException: Could not load file or assembly 'ASAM.XIL.Implementation.Testbench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=a258c402a414cddb' or one of its dependencies. The system cannot find the file specified.
File name: 'ASAM.XIL.Implementation.Testbench, Version=2.0.1.0, Culture=neutral, PublicKeyToken=a258c402a414cddb'
at ETAS.EE.XIL.API.Testbench.LabCarTestbench.get_ValueFactory()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
it seems from the error it is not able to locate the testbench files whereas the testbench files are located in the same folder.