The issue is present when JustMock extension is installed and the debugger is launched inside unrelated projects, for example, a blank console app. The extension should detect JustMock references from project settings and automatically disable this feature when it becomes inapplicable. Optionally the extension could give the way to explicitly disable the debug window from popping up by toggling the menu item.

Currently, the JustMock tests are failing when the Live Unit testing functionality is started. JustMock should provide integration for the Visual Studio Live Unit testing functionality.

JustMock configuration tool requires admin users for toggling integration with 3-rd party profilers which might become a blocker for using it in the CI pipelines.

Currently, when the JustMock profiler is enabled it provides a performance hit on the test execution. This effect is expected because a profiler is involved.

What we can do is find a more optimized way of instrumenting the methods.

Implement support for VS Code.

Currently, the Debug Window could be used only with one instance of Visual Studio. The goal of this feature is the Debug Window to support multiple independent instances of Visual Studio.

Docker is a container acting like an isolated environment. Research how the JustMock profiler can be registered into such container.
Hosted VSTS should work on the same principle. Research how the registry could be accessed through VSTS extension or other tools.

JustMock should support .NET 5

The Add/Update JustMock reference is shown for .NET Core projects but without implementation it does nothing.

In some cases, the working directory of the test execution needs to be changed to a dedicated path. Currently, it is not possible out of the box, as a workaround can be used start command.

Currently, the support for code coverage in the JustMock Azure Pipeline task includes only projects targeting .NET Framework.

Implement support for projects targeting .NET Core.

Currently, there are a lot of JustMock project templates with different targeted categories. There are templates targeting just one search category and there are other templates targeting different categories.

Optimize the templates to be available in all relevant search categories and lower their number.

Just like the core mocking API has ArrangeSet/AssertSet methods, so should the MockingContainer have them.

The JutMock task for Azure Pipeline is missing the option to execute the tests with Visual Studio 2019. Check the attached screenshot.

.Net for application developers prefer writing their build script using cake. It is necessary for JustMock to have a cake utility to work with. 

Consider the scenario where a class has a string field which is his main data. This class has defined an implicit cast operator to string. When that cast operator is executed the resulted string will contain the value from the class field.

Implement support for mocking of an operator such as the one described. 

The CallMethod of the PrivateAccessor is using reflection to invoke the required method. When an exception is thrown inside that method it will be wrapped by the reflection in a TargetInvocationException which is received in the test method.

Instead of the TargetInvocationException, throw the original exception.

Elevated unit testing does not work with NET Core SDK 3.0.100 - preview8

Implement support for future mocking of public class with non-public arguments.
Such example is the future mocking of the class Timer with a private callback.