Current filter:
                                You should refresh the page.
                                  • 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

                                • Alex Z (DevExpress) 12.11.2018

                                  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.

                                • Chris Gorringe 12.11.2018

                                  Hi Alex.
                                  This morning I have just finished doing this to try and find the problem:

                                  1. As I was running VS as administrator for elevated permissions, I had to run it without elevated permissions to allow me to export my settings. It simply would not give me any dialog when running elevated.
                                  2. I then uninstalled CodeRush and then deleted all my CR settings and entries in the user profile.
                                  3. I deleted all the obj and bin folders for all the projects in the solution.
                                  4. I then ran VS without elevation and reinstalled CR and imported my settings.
                                  5. If I attempt to debug without elevated permissions, it now appears to work fine but if I attempt to debug with elevated permissions, it hangs as soon as I click on a button in the form. If I click anywhere in the code in this state, I get the Delay Notificaiton from VS asking to Switch to or continue waiting. If I choose anything, I get the sping blue wheel and VS has (Not Responding) in the banner. The only way out is to kill the winform task that I am debugging. Sometimes I get the yellow banner saying the CodeRush has taken X seconds to respond etc.
                                  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.

                                • Chris Gorringe 12.11.2018

                                  Hi Alex
                                  Further investigation has shown this:

                                  1. Once I ge the probelm in elevated mode, the problem then appears in non-elevated mode.
                                  2. I have tracked down the line of code that is starting the problem. Clipboard.SetDataObject("sometext"); As this point, the debugger leaves this line highlighted and gets stuck. If I remark this line out, debugging works fine.

                                  Is there a clipboard monitor or somesuch in CR that may be getting stuck and how can I tell?

                                • Alex Z (DevExpress) 12.11.2018

                                  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.

                                • Chris Gorringe 12.11.2018

                                  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. 

                                1 Solution

                                Creation Date Importance Sort by

                                Fixed: