Azure pipeline with task Telerik JustMock VSTest v.2 failed on new build server

[SIEN]

Hi,

on a new build server with only Visual Studio 2022, a pipeline with a task Telerik JustMock VSTest v.2 failed. On another build server the task runs fine but this server has Visual Studio 2017 and 2019.

With only Visual Studio 2022, I see this in the logs :

2024-10-29T08:40:10.1079920Z ##[debug]E:\AzureDevOps\Agents\Cloee2Agent1\_work\_tasks\JustMockVSTest_dfc18792-8901-4297-a4de-6edef6796070\2.4.1\vswhere.exe arg: -version [16.0,17.0) -latest -products * -requires Microsoft.VisualStudio.PackageGroup.TestTools.Core -property installationPath

2024-10-29T08:40:10.1080395Z ##[debug]exec tool: E:\AzureDevOps\Agents\Cloee2Agent1\_work\_tasks\JustMockVSTest_dfc18792-8901-4297-a4de-6edef6796070\2.4.1\vswhere.exe

2024-10-29T08:40:10.1080699Z ##[debug]arguments:

2024-10-29T08:40:10.1080925Z ##[debug]   -version

2024-10-29T08:40:10.1081156Z ##[debug]   [16.0,17.0)

2024-10-29T08:40:10.1081399Z ##[debug]   -latest

2024-10-29T08:40:10.1081624Z ##[debug]   -products

2024-10-29T08:40:10.1081840Z ##[debug]   *

2024-10-29T08:40:10.1082053Z ##[debug]   -requires

2024-10-29T08:40:10.1082310Z ##[debug]   Microsoft.VisualStudio.PackageGroup.TestTools.Core

2024-10-29T08:40:10.1082557Z ##[debug]   -property

2024-10-29T08:40:10.1082780Z ##[debug]   installationPath

 

The call to vswhere ask for version "[16.0,17.0)". In the properties of the task I specify "Test Plateform Version : Latest". So why is vswhere searching only for version 16 and 17 ?

Thank you

 

[Ivo]

Hello there,

I apologize for your negative experience with the JustMock task. This issue has been reported recently and is being addressed for a fix. I appreciate your patience while we work on this.

Regards,
Ivo
Progress Telerik

[SIEN]

In the end, the problem was the version of the extension in Azure Devops. As our server had no access to the Internet, Azure told me that the version installed was the latest, but this was not the case. After updating to version 2.0.14, everything worked perfectly.

Thank you, regards

[Ivo]

Thanks for the update! I am happy to hear that the issue has been resolved.

[SIEN]

See my last comment