Devart Forums

Not sure how you got it to show up in VS2022 as even being enabled without hacking around a bit. VS2022 is 64 bit and some of the techniques used in extensions in prior versions (which used 32-bit COM behind the scenes) are not easily moved to VS2022. There may be more effort required to move it to 2022 than you may think.

That said, recent posts in this forum (and also Review Assistant) have been responded to with:

Development is complex and creative work. In spite of our willingness to continue expanding our product, we must evaluate our efforts, and currently, we do not develop Code Compare actively.

DevArt has not marked the product with this status on their product page, and will continue to gladly take your money for license renewals, however. I also do not know if folks that buy VS2022 can downgrade and also have VS2019 to continue using Review Assistant. Having two versions of VS to move between for your workflow is sub-par anyway.

I'd love to get more than the form letter in response to this request here. We are considering expanding use of this tool to other business units which means we need to buy more seats (the bundle with Review Assistant). If it will not at least receive minimal updates to maintain functionality on newer versions of its dependencies, we will use alternative solutions. And we need to decide very soon if we move off this tool or not as our license renewal is coming up.

Not sure how you got it to show up in VS2022 as even being enabled without hacking around a bit. VS2022 is 64 bit and some of the techniques used in extensions in prior versions (which used 32-bit COM behind the scenes) are not easily moved to VS2022. There may be more effort required to move it to 2022 than you may think.

That said, recent posts in this forum (and also Code Compare) have been responded to with:

Development is complex and creative work. In spite of our willingness to continue expanding our product, we must evaluate our efforts, and currently, we do not develop Review Assistant actively.

DevArt has not marked the product with this status on their product page, and will continue to gladly take your money for license renewals, however. I also do not know if folks that buy VS2022 can downgrade and also have VS2019 to continue using Review Assistant. Having two versions of VS to move between for your workflow is sub-par anyway.

I'd love to get more than the form letter in response to this request here. We are considering expanding use of this tool to other business units which means we need to buy more seats (the bundle with Code Compare). If it will not at least receive minimal updates to maintain functionality on newer versions of its dependencies, we will use alternative solutions. And we need to decide very soon if we move off this tool or not as our license renewal is coming up.

I have an idea for DevArt. Please post an example of real-world use that you consider acceptable performance, including the specs of the PC and your timings. If our real-world use experiences differs from that, we will send diagnostic data.

I have not found a single example where startup time is what I would consider not excessive. I am surprised you need us to provide diagnostic data when this is the norm, not the exception.

The DevArt Review Assistant Service fails to start if the SQL database is not available. Although it is set as Automatic (Delayed Start), our database is on a different server, and when performing server maintenance at times the SQL Server has not finished its reboot when the DevArt Review Assistant Service starts and it fails to start. This being a rather standard use case, I am surprised not to see other forum posts regarding this. Can you please fix it?

Thanks,
Steve

FYI, there is also a post regarding this from resharper: https://blog.jetbrains.com/dotnet/2019/ ... awareness/

Additionally, I also see the 'gold bar of slowness' blaming CodeCompare, even when there are no code compare windows open, nor were any open for that specific session.

Any update from your side on either of these issues?

An update to one of the issues I linked to indicates this is, in fact, an issue with Code Compare.

Per-monitor support in Visual Studio requires extenders to review their UI for compliance (and is one of the reasons we provide a way for you to disable the feature). This documentation is available here: https://docs.microsoft.com/en-us/visual ... ew=vs-2019.

Code Compare Version 5.1.156, Visual Studio 2019 RTM, Review Assistant 4.1.237, TFS 2018 (latest patch), Windows 10 Build 1904

I am seeing a blank comparison tab when doing a diff using DevArt Code Compare. Also in Visual Studio WinForms editor, viewing Tab Order does not show the order labels. I found that disabling the Visual Studio setting found in Option->Environment->General->"Optimize rendering for screens with different pixel densities" makes both work. Not sure if this is a .NET, Windows, Visual Studio, or Dev Art issue. A similar issue existed for some Visual Studio windows that was marked fixed prior to RTM: https://developercommunity.visualstudio ... -empt.html so perhaps it is something that the provider of the windows content needs to do to be compatible with this setting if it was truly resolved.

Environment: Windows 10 1904 RTM, VS Enterprise 2019 16.0.2, Dell Precision 7730 with Radeon Pro WX 4150 Graphics driver version 23.20.15025.13004 running two 96 dpi monitors and the built in Intel UHD Graphics 630 version 25.20.100.6519 running the built-in 127 dpi display (which incidentally is off so technically the only monitors enabled have same density).

See also https://developercommunity.visualstudio ... des-1.html and https://developercommunity.visualstudio ... for-s.html