Skip to main content

Obsolete warning when using just installed VS extension



1 comment

  • Jordan Western

    Hi Rob,

    Thanks for reaching out.

    I think this is fine because the reference to the static scenario context is not intended to be permanent and we cannot assume that the class already has access to the ScenarioContext object via context injection as this would throw a build error of course.

    Here is a link to the bug to resolve this issue -

    We will have this resolved in the VS2022 version of the extension.

    Thanks, Jordan.


Please sign in to leave a comment.

Powered by Zendesk