Hi Dojo
I noticed that some people were unable to run the unit tests of a specific protocol right after they cloned the repo. When they open the QActionTests.cs file, each link towards the QActionHelperBaseClasses.dll file is underlined in red:
As you can see below, the reference to the QActionHelperBaseClasses.dll is marked with an warning sign:
I didn’t get these errors when I pushed the code through the pipeline to the server so I was confused when I found out that other people could not run the tests. Only after buidling the solution in Release mode I could see these errors as well. Manually removing the QActionHelperBaseClasses.dll reference and adding it again solved the issue.
I’m expecting that everybody can run my tests after they have cloned the repo without further manual adjustments. Did I do something wrong when I pushed the code to the server or could there be en issue with the QActionHelperBaseClasses.dll?
Thank you in advance!
Hi Michiel,
I’m not sure if this is the case for the QAHelperBaseClasses, but in general, you can choose if a referenced .dll is using a specific version or not in the reference properties. In some cases setting this to false can make handling of updated .dll’s easier. See the example below – a screenshot of a System.Core.dll reference.
