I installed DevEx Ver 17.1.6 yesterday and have been converting and recompiling my programs. All has gone smooth except for one program. Visual Studio locks up when the program loads then goes into a loop where it shuts now and restarts (locking up when it restarts of course). There is a message below the toolbar that says "UseStringFormatCodeFix encountered an error and has been disabled". Then two buttons "Enable" and "Enable and ignore future errors" (see attached image). Can't click either button because VS is locked up. The only delta with this program has been the installation of the new DevEx. There is no sub routine or reference to "UseStringFormatCodeFix" in the program so I was hoping you could shed some light on this. Looks like maybe something from Code Rush? I will also admit that I installed what someone else had downloaded for us without paying too much attention and the Code Rush version is 17.1.8 (the DevEx is Ver 17.1.6). I've restored several back ups converted them and get the same result. Other programs still load, compile and run fine. Any ideas?
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Richard,
You right, the message with "UseStringFormatCodeFix" can be related to CodeRush. Could you help us and perform the following steps to fix the problem or understand its cause:
Sorry for the delay - other fires to put out. I have updates in the Tools->Extensions but Code Rush was not one of them. I did disable Code Rush and the problem program loaded just fine. Attached is a zip file with the logs. Take your time with the analysis, I'm good for now. Sorry there are so many logs but I've been recompiling quite a bit. Thanks for your help.
Thank you for the log files. I have analyzed them and found the following error in three different log files:
Error: Message: Object reference not set to an instance of an object.
Error: Type: System.NullReferenceException
Error: Source: DevExpress.CodeRush.VSTestRunner
We have prepared a special build containing a fix for the problem.
Can you please install it, disable CodeRush via the Visual Studio extension manager: Tool -> Extensions and Updates… -> Installed -> All -> CodeRush for Roslyn -> Disable button, restart Visual Studio, try to reproduce the problem and provide us with your results?
If the problem persists after installing the CodeRush build with the fix, this will mean that the problem is related to a certain specificity of your project or to other extensions installed in your Visual Studio. Could you then share your Visual Studio information about the extensions installed on your side? For this, click the "Copy Info" button in the "About Microsoft Visual Studio" dialog and post the resulting information here. This information can help us reproduce the problem on our side.
Dmity, I too have encountered the same issues as described in this post. No errors present in the CodeRush logs, other than the warning within VS 2015 that 'UseStringFormatCodeFix' has encountered issues and has been disabled.
The special build did the trick. Everything is working fine. It has been checked out on the problem program and some of the previous working ones just to make sure - they are all ok. Many thanks to you and the group.
Richard, you are welcome.
I am happy to hear that the problem is solved. Thank you for letting us know about this.
Mark, did you have the opportunity to try this build? Does it fix the problem on your machine as well?
So far so good Dmitry. If I do see this happening again I will comment on this ticket.
OK, thank you for letting us know.