I'm getting the following execption Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables.

Surya Pattepu 6

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator1.CommonInit() at System.IO.FileSystemEnumerableIterator1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetDirectories(String path)

the offending line is :

using (ShimsContext.Create())

BhargaviAnnadevara-MSFT 5,466 Reputation points

2021-05-26T12:41:35.68+00:00
@Surya Pattepu Thanks for reaching out. Could you please provide us the complete code snippet to troubleshoot this further?
Which version of VS is this occuring with?

Do check if the following resources help:

Testing.Fakes Exception

Isolate code under test with Microsoft Fakes

Use shims to isolate your app for unit testing
Surya Pattepu 6 Reputation points

2021-05-27T05:24:45.083+00:00

We are using Microsoft Visual Studio Enterprise 2019 Version 16.9.4
In our local envmnt units tests (both normal unittest methdos and unitests with MSFakes) are running successfully.
When trying to execute unit tests some are working fine and unit tests which use the MSFAKES framework
Error CS0234: The type or namespace name 'Fakes' does not exist in the namespace 'XXX'all of them fail on the build server with error.
In build server Fakes aren't generated
checkin FakesAssemblies folder and the issue is resolved.(is this correct approach or not?)

After resolving this issue , now we are getting below error message in build server.
Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables.

How can I fix that?
BhargaviAnnadevara-MSFT 5,466 Reputation points

2021-05-27T06:10:54.053+00:00

@Surya Pattepu Thanks for the response and additional details. Retagging for the appropriate team to look at the issue.
Tianyu Sun-MSFT 30,566 Reputation points Microsoft Vendor

2021-05-27T09:58:50.34+00:00

Hi @Surya Pattepu , did you use MSTest.exe or vstest.console.exe? I see that you are using VS 2019 Enterprise version, and as you know Microsoft Fake framework is supported by using VS Enterprise, please kindly check if your build server also uses/depends on VS 2019 Enterprise version.
Surya Pattepu 6 Reputation points

2021-05-27T12:24:18.783+00:00

Build server also installed VS 2019 Enterprise version.
Tianyu Sun-MSFT 30,566 Reputation points Microsoft Vendor

2021-06-02T07:08:10.507+00:00

Hi @Surya Pattepu , thank you for your feedback. Did you use a .testsettings file? Did you use some third-party extensions for example ReSharper?
Surya Pattepu 6 Reputation points

2021-06-02T15:26:38.963+00:00

I'm not using .testsettings file and not used third-party extensions
Tianyu Sun-MSFT 30,566 Reputation points Microsoft Vendor

2021-06-10T07:55:33.047+00:00

Hi @Surya Pattepu , may I ask, how you run the test on your build server? Did you use some features of the application to run the test? I’m considering if this issue is caused from the specific application/engine/feature of your build server side. Besides, this could be a potential issue.

Share via

I'm getting the following execption Microsoft.QualityTools.Testing.Fakes.UnitTestIsolation.UnitTestIsolationException: Failed to resolve profiler path from COR_PROFILER_PATH and COR_PROFILER environment variables.

Your answer