Devart Forums

I read the other post about Visual Studio 2022. We just went through the process of working with Devart sales to purchase another license for Review Assistant. We told support specifically this was so we could upgrade to Visual Studio 2022 since our old version of Review Assistant wasn't compatible with Visual Studio 2022. We took a server side upgrade as well to go along with this.

When I install, and check the box for Visual Studio 2022 integration, it doesn't show up in any menu. I can see that it is installed in the extensions tool, but cannot figure out how to make it available to use. I don't have any menu items or the right click option on a file in source control explorer like there used to be in Visual Studio 2017.

Please let me know if I am doing something wrong, or if I need to download and install a different client version.

Can someone from Devart support respond to this message. I sent an email and used the contact feature on the website yesterday but haven't heard back yet.

Thanks,
-Wayne

We have ReviewAssistant v3.6.450 and are seeing all the reviews being saved with UTC time. Is there a setting, or a way to make them show up as eastern time. We are using the API for a custom report and are hoping there is a setting somewhere that I am missing.

Thanks

What is the difference and intended usage of a 'Regular Review' vs the 'Initial Review' that I can create from the Code Review Board?

Thanks.

Hi. We are working with the trial and need to know how to do something. We need to be able to run a code coverage report on a specific branch at a time. We only see how to get a report on the root project. Our TFS source control repo is setup like this

• Development (TFS Project)
  • Trunk
    Releases
    Branches
    • Feature1
      • UAT
        DEV
      Feature2
      • UAT
        DEV
      Feature3
      • UAT
        DEV

We need to do code reviews in DEV and then check that all change sets have an accepted code review before the manager merges the changes to UAT for testing then to trunk for release.

We will have multiple branches with code in different stages of development. The current report shows all paths and it is confusing when looking specifically at a specific branch.

Is this possible, and if so, how do we do it?

Thanks,
-Wayne