{"id":34065,"date":"2024-04-25T19:25:27","date_gmt":"2024-04-25T19:25:27","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=34065"},"modified":"2024-04-25T20:11:18","modified_gmt":"2024-04-25T20:11:18","slug":"visual-studio-features-for-c-header-files-and-modules","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/visual-studio-features-for-c-header-files-and-modules\/","title":{"rendered":"Visual Studio features for C++ Header Files and Modules"},"content":{"rendered":"

In the field of C++ programming, the management of header files and modules can often seem challenging. However, there are numerous tools and features available that can simplify this process, enhancing efficiency and reducing the likelihood of errors. Here\u2019s a walkthrough for several tools that we provide for C++ headers and modules.<\/p>\n

Run Build Insights<\/h3>\n

Start by running Build Insights,<\/a> through navigating to Build <\/strong>> Run Build Insights<\/strong>.<\/p>\n

\"Image<\/a><\/p>\n

This tool provides insights into the Include File and Include Tree views to analyze and optimize your #include usage. For instance, in the bullet3<\/a> sample repository, running Build Insights reveals that the overall build time of our current project is 202.812 seconds.<\/p>\n

\"Image<\/a><\/p>\n

<\/h3>\n

Enable #include Cleanup<\/h3>\n

Next, enable the #include cleanup<\/a> feature (Tools <\/strong>> Options <\/strong>> Text Editor<\/strong> > C\/C++ <\/strong>> Code Cleanup <\/strong>> Enable #include cleanup<\/strong>). This feature helps remove unused #include directives and add transitively used headers. You can also adjust the severity of the suggestion levels to suit your coding style and requirements.<\/p>\n

\"Image<\/a><\/p>\n

<\/h3>\n

Configure #include Cleanup<\/h3>\n

You can also customize how #include cleanup generates suggestions using EditorConfig<\/a>. You can exclude specific includes, specify dependencies, remap headers, and specify alternatives using the setting in Configure Include Cleanup with .editorconfig.<\/a><\/p>\n

Use #include Cleanup<\/h3>\n

Utilize the lightbulb in the editor for the following tasks:<\/p>\n

Adding Transitively Used Headers<\/strong>: Add indirectly used includes individually or all at once.<\/p>\n

Removing Unused Headers<\/strong>: Remove unused includes individually or all at once.<\/p>\n

Optimizing Include Graph for this file<\/strong>: Add all transitively used includes and remove unused ones for an optimized include structure.<\/p>\n

Let\u2019s apply this to the \u2018test_invdyn_jacobian.cpp\u2019 file in our sample repo. Choose \u201cOptimize include graph for test_invdyn_jacobian.cpp\u201d<\/p>\n

\"GIF<\/a><\/p>\n

<\/h3>\n

Check Build Time Improvement<\/h3>\n

After cleaning your \u2018test_invdyn_jacobian.cpp\u2019 file, run Build Insights again to quantify the benefits of your cleanup efforts. In our sample repo, the overall build time improved to 197.76 seconds.<\/p>\n

The #include cleanup feature doesn\u2019t clean your entire project all at once. But you can use it to gradually improve your project. Focus on the parts that take the longest to build. You can find these parts using Build Insights. The more files you clean, the faster your project will build.<\/p>\n

\"Image<\/a><\/p>\n

<\/h3>\n

Enable #include Diagnostics<\/h3>\n

The #include Diagnostics<\/a> feature allows you to view the usage and build time of your header files directly in your editor.<\/p>\n

Turn On #include Diagnostics<\/h3>\n

Turn on #include diagnostics by right-clicking on the editor to open the context menu, navigating to the \u2018#include Directives\u2019 option, and choosing \u201cTurn #include Diagnostics On\u201d. This will display CodeLens above each of your header files, providing information about their usage and build time.<\/p>\n

Upon evaluating the build time and usage of each header file, you can employ the #include cleanup feature to refine your headers. This action can markedly improve the overall build time of your project. The reason behind this is that any unused include directive within these headers can cause an unnecessary expansion of the graph wherever the header is utilized. By removing these, you are effectively making the build process more efficient.<\/p>\n

\"GIF<\/a><\/p>\n

<\/h3>\n

Use Modules in C++20<\/h3>\n

In addition to the features mentioned above, C++20 introduces Header Units and Named Modules.<\/p>\n

Header Units<\/strong> serve as a bridge between traditional header inclusion and named modules. They allow you to import header files as modules, providing a faster and more robust alternative to the traditional #include. Importantly, they don\u2019t require any changes to your header files but do need significant modifications to your build system.<\/p>\n

Named Modules<\/strong> offer superior performance and control over what they export. They require the creation of .ixx files and the addition of export keywords. The order of imports doesn\u2019t matter due to their order-independence and macro-independence.<\/p>\n

To dive deeper into these features, check out the Overview of modules in C++<\/a> and Walkthrough: Build and import header units in Visual C++ projects<\/a> on Microsoft Learn.<\/p>\n

 <\/p>\n

Send us your feedback<\/h3>\n

We value your input! If you have any insights, suggestions, or requests, please let us know in the comments section below or\u00a0<\/span>in the\u202f<\/span>Developer Community<\/span><\/a>. You can also reach out to us on Twitter (@VisualC<\/a>) or via email at\u00a0visualcpp@microsoft.com<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

In the field of C++ programming, the management of header files and modules can often seem challenging. However, there are numerous tools and features available that can simplify this process, enhancing efficiency and reducing the likelihood of errors. Here\u2019s a walkthrough for several tools that we provide for C++ headers and modules. Run Build Insights […]<\/p>\n","protected":false},"author":96741,"featured_media":34083,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-34065","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus"],"acf":[],"blog_post_summary":"

In the field of C++ programming, the management of header files and modules can often seem challenging. However, there are numerous tools and features available that can simplify this process, enhancing efficiency and reducing the likelihood of errors. Here\u2019s a walkthrough for several tools that we provide for C++ headers and modules. Run Build Insights […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/34065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/96741"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=34065"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/34065\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/34083"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=34065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=34065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=34065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}