In my current development VM , I have been using VS2017 with Coderush without an issue. I periodically update the VS2017 and I am currently on 15.9.3 Professional. I also have Coderush set to automatically update and it is currently CodeRush for Roslyn 18.2.4.0.
Since the last update (CodeRush or VS - not sure), I am getting a problem as follows:
I have a Winforms app that I have developed over the years and I peridoically update it as required. If I have CodeRush enabled and start to debug the app, I never get to any break points and VS 2017 completely hangs until I kill the process that I am debugging. If I disable CodeRush, everything returns to normal. I already have the Debug Visualizer disabled.
Can you suggest a nything to resolve this problem?
Many thanks
Chris
Performance - CodeRush slows down in Visual Studio 2017 when debugging (or in debug mode)
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
- v18.2.5Download Official Update
Chris,
We are concerned about this issue. Please help us diagnose and fix it by providing answers to the questions below and some additional information.
Is this reproducible in a specific application and with specific debugging steps?
Can you reproduce this in a newly created WinForms application?
Please try to attach another Visual Studio instance to the hanging Visual Studio process and collect stack traces of the running threads.
Looking forward to hearing from you.
Hi Alex.
This morning I have just finished doing this to try and find the problem:
If I disable CR, everything works fine so I don't think that reinstalling had any benefit.
If VS is unresponsive, how do you want me to gather the stack traces etc.
Hi Alex
Further investigation has shown this:
Is there a clipboard monitor or somesuch in CR that may be getting stuck and how can I tell?
Chris,
Great, thank you for the investigation. Yes, CodeRush indeed has a clipboard monitor, it is used in a clipboard history feature.
I have reproduced this issue with the Clipboard.SetDataObject code. I think we can disable a clipboard monitor when debugging. Please give us some time to address this.
I am so gald that I raised this as an issue and persevered with trying to work out what was causing it.
Let me know when you have a fix.