This is something we have addressed in SP1, but even still, the error window can be a good place to start investigating performance issues. In VS2010 RTM, errors in your PCH will prevent the IntelliSense compiler from creating a PCH. This blog post will be focused on what to do when you’ve followed those steps and things still aren’t working for you. I have previously written a blog post on the PCH model and how to configure it within the IDE. Getting your PCH settings right are also vital to having fast builds – so getting this right can potentially be a boon on two fronts. For large C++ translation units (and most of the ones that you care about are going to be large), IntelliSense PCH is vital to ensuring fast IntelliSense. Having spent a lot of time helping customers with slow IntelliSense, I have found that their performance issues are almost always related to PCH being disabled. The goal of this article is to assist you in troubleshooting this complex system, and give you a peek under the hood at how it works (and what to do when it doesn’t). The IntelliSense system in Visual Studio 2010 comes with far greater power, flexibility, and accuracy, but these improvements come at the cost of greater complexity. Hi, my name is Andy Rich and I’m a QA on the C++ front-end compiler.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |