Known Issues for Visual Studio Plug-in

This topic includes the known issues and workarounds for the Visual Studio plug-in.

• Visual Studio 2019: When you perform an 'add to ignore', a .acignore file is created. However, the .acignore file is not updated accordingly when you repeat the 'add to ignore' or 'remove from ignore' command on the same or different file.

  Workaround: Manually add files to be ignored in the .acignore file and refresh. The files will be ignored.

• Visual Studio 2019: While closing the solution, if you undefunct a file in the “defunct overlap kept member” status in the commit window, an error message displays: “AccuRev undefunct failed". The undefuncted file does not get added back to the solution when the solution is re-opened.

  However, the file gets undefuncted and its status changes to "overlap kept member". The file is also becomes available in the file explorer.

  Workaround: In the Visual Studio solution context menu, select Add > Existing Items, navigate to the file location and manually add the undefunct files to the solution again.

• Visual Studio 2019: While closing the solution, if you purge a file in the “defunct overlap kept member” status in the commit window, an error displays, and the file does not get added back to the solution.

  However, the purge is successful and the file status changes to “backed stale”. The file also becomes available again in the file explorer.

  Workaround: In the Visual Studio solution context menu, select Add > Existing Items, navigate to the file location and manually add the purged files to the solution again.

• Visual Studio 2019: While using AccuRev Visual Studio plug-in in Visual Studio 2019, the pop-up windows (such as the AccuRev, AccuRev Depot Explorer, and AccuRev Workspace Explorer windows, and so on) do not load with contents. The pop-up windows are empty and transparent.

  Workaround: In the Visual Studio menu, select Tools > Options, the Options window opens. From the navigation pane, select Environment > General. In the Visual Experience section, deselect the "Optimize rendering for screens with different pixel densities (requires restart)" check box, and then restart Visual Studio for the changes to take effect.

• If Visual Studio is running on a system which is connected via an RDP session, the decorators might display inconsistently.
• In AccuRev 6.0 and 5.7, the executable for the AccuRev Diff tool, acdiffgui.exe, did not list all of the jar files needed to run the AccuRev Diff tool from within AccuRev Plug-In for Visual Studio PE. This prevented users with AccuRev 6.0 or 5.7 from using the AccuRev Diff and Merge tools from AccuRev Plug-In for Visual Studio PE. This problem has been corrected in AccuRev 6.0.1. If you recently upgraded to AccuRev 6.0, you should upgrade to 6.0.1. If you are using either 6.0 or 5.7 and do not plan to upgrade, contact Support Line.