Скачать или смотреть How to Make VS Code IntelliSense Work with .mm File Extensions

Learn how to set up Visual Studio Code to enable `IntelliSense` and `Go to definition` features for `.mm` files by changing associations.
---
This video is based on the question https://stackoverflow.com/q/75256192/ asked by the user 'asmbaty' ( https://stackoverflow.com/u/4910232/ ) and on the answer https://stackoverflow.com/a/75261261/ provided by the user 'The Dreams Wind' ( https://stackoverflow.com/u/5690248/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to make VS Code IntelliSense work with `.mm` file extentions?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Make VS Code IntelliSense Work with .mm File Extensions

If you've been working with Visual Studio Code (VS Code) and used the .mm file extension for Objective-C+ + files, you may have encountered a frustrating issue: IntelliSense and the Go to definition feature suddenly stop functioning properly. This can hinder your development experience, especially when you rely on these features for coding efficiency and accuracy.

In this guide, we will delve into the problem and provide a step-by-step solution to ensure that IntelliSense works seamlessly with .mm files.

Understanding the Problem

By default, VS Code treats different file extensions differently, employing various language modes based on that extension. When you change a file from .cpp (which is C+ + ) to .mm, VS Code might not correctly recognize the file as belonging to the C+ + language, leading to reduced support for features like IntelliSense and Go to definition.

Solution Overview

To restore full functionality for .mm files in VS Code, you need to update the settings.json file in your project. This change will instruct VS Code to treat any .mm files as if they are C+ + files. Here’s how you can do that:

Step-by-Step Instructions

Open VS Code: Launch your Visual Studio Code application and open your working project.

Access the settings.json File:

Go to the Explorer pane on the left-hand side.

Locate and open the .vscode folder within your project directory.

Find and open the settings.json file. If the file does not exist, you can create a new one.

Modify the settings.json File:
In the settings.json file, add an association for .mm files. Your settings should look something like this:

[[See Video to Reveal this Text or Code Snippet]]

Save Your Changes: After you've made the necessary modifications, save the settings.json file.

Verify IntelliSense Functionality: Reload your project or reopen the .mm files to confirm that IntelliSense and Go to definition features are now working.

Important Considerations

While associating .mm files with C+ + can resolve the issue quickly, be aware of the following:

Language Differentiation: VS Code can distinguish between Objective-C and Objective-C+ + languages. Changing file associations may lead to loss of specific language support features that you could benefit from.

Language Server Extensions: As of now, there may not be a viable language server extension dedicated to Objective-C or Objective-C+ + . Keep this in mind when working with these file types, as the support might be limited.

Conclusion

By following the simple steps outlined in this guide, you can effectively get IntelliSense and Go to definition working with .mm file extensions in Visual Studio Code. This adjustment not only streamlines your coding workflow but also helps you harness the potential of VS Code's powerful features for C+ + development.

If you encounter any further issues or have additional tips, feel free to share your experiences in the comments!