Posts Tagged ‘Troubleshooting’

Resolving code template conflicts

September 30th, 2012 Comments off

Sometimes, you may find unexpected code template expansions when you typing code. This may happen when the template expansion key is bound to the Space Bar. Because this is a key used very often and there are tens of thousands of code templates; a complex contexts system, something may go wrong, especially if you prefer one or two key identifier names which may correspond to existing template abbreviations.

Read more…

Troubleshooting the DXCore/CodeRush plug-in loading

May 15th, 2012 2 comments

Sometimes CodeRush/DXCore plug-ins may not be loaded correctly. Here is a brief instruction if you’d like to investigate and fix the loading of the plug-in in question.

Read more…

How to speed up the issue investigation time and help to eliminate complex problems

May 15th, 2012 Comments off

If you ran into an unusual problem, you may greatly help the DevExpress Support Team in investigating the issue by providing as much information as possible. Having this information will increase the chances and the speed that the issue will be fixed. Once the issue is fixed, you are always welcome to request a daily build containing the fix from the Support Team.

Read more…

CodeRush Tool Windows – Message Log

July 5th, 2011 Comments off

The Message Log is a CodeRush/DXCore diagnostics tool window that records a history of important IDE Tools and Visual Studio events live. The window is useful for diagnostic purposes and finding clues to unexpected DevExpress IDE Tools behavior. To open it, click the DevExpress | Tool Windows | Diagnostics | Message Log menu item:

Read more…

How to debug DXCore plug-ins under Visual Studio 2010 SP1

March 17th, 2011 5 comments

Visual Studio Service Pack 1 introduced an issue that prevents breakpoints to be hit while debugging DXCore plug-ins. When you hit F5 to run the plug-in project, Visual Studio builds it and starts the second instance of Visual Studio where you can debug the plug-in. However, the breakpoints inside plug-in project won’t be hit when you have SP1 installed. The corresponding bug report is registered on the MS Connect. It seems that the issue is in the TargetFramework version set for the project: if the version is 2.0 – the break point won’t be hit.

Read more…

Unbound Actions – Clear Project Cache

February 16th, 2011 Comments off

The Clear Project Cache action invalidates the IDE Tools cache for the current solution. The solution cache represents an on-disk cache, containing important information for all projects for every solution you had opened, such as metadata, project symbols, code issues stuff, etc. This cache is built for every solution while it is opened and parsed, and maintained by DXCore automatically.

Read more…

What is the best way to report an IDE tools issue

January 18th, 2011 Comments off

The most preferred and official way to report issues in DevExpress’ products is the Support Center. This is the primary channel where you can get answers to your questions, report bugs and make suggestions. Whenever you want to create a new issue (ask a question, post a bug or a request), they will advise that you look through the currently posted issues. A similar issue may already have been reported, so you’ll find a quick answer.

Read more…

Tools cooperation – Visual Assist X and IDE Tools

December 9th, 2010 3 comments

Here is the result of testing the Whole Tomato’s Visual Assist X and DevExpress’ IDE Tools co-existence for those, who prefer to use features of several Visual Studio productivity tools working side-by-side at once.

Tested versions:

  • VAX – 10.6.1833.0
  • IDETools – 10.2.3

Read more…