Carb sdk intellisenece error

Omniverse Core Platform Kit App Template / SDK
1

Operating System:
Windows
Linux
Kit Version:
110 (Kit App Template)
109 (Kit App Template)
108 (Kit App Template)
107 (Kit App Template)
106 (Kit App Template)
105 (Launcher)
Kit Template:
USD Composer
USD Explorer
USD Viewer
Custom
GPU Hardware:
A series (Blackwell)
A series (ADA)
A series
50 series
40 series
30 series
GPU Driver:
Latest
Recommended (573.xx)
Other
Work Flow:
Main Issue:

After adding:

include <carb/dictionary/IDictionary.h>

and using:

carb::dictionary::IDictionary* temp = nullptr;

Visual Studio reports IntelliSense error E0135:

“namespace ‘carb::dictionary’ has no member ‘IDictionary’”

However, the project builds successfully and the extension runs correctly without any compiler or runtime errors.

This appears to be an IntelliSense-only issue. I would like to know whether this is a known issue with Omniverse Kit C++ extensions and if there is a recommended way to configure IntelliSense so that carb::dictionary::IDictionary is recognized correctly.
Reproduction Steps:
Error Code: E0135

2

At the moment, I do not see an NVIDIA document that gives a specific Visual Studio IntelliSense fix for this exact IDictionary case in Kit 110.

What is reasonable to try in Visual Studio is:

  • Regenerate the solution/project from the Kit template so IntelliSense databases are rebuilt.
  • Force a full IntelliSense rescan by deleting .vs, ipch, and generated browse database files, then reopening the solution.
  • Verify the affected .vcxproj configuration exposes the same include directories and preprocessor definitions to IntelliSense as to the actual build configuration. The build succeeding strongly suggests a mismatch here rather than bad code.
  • Prefer relying on the compiler result over E0135 for this symbol unless NVIDIA publishes an SDK-side workaround.

Recommendation

Based on the available evidence, I would treat this as a known-or-at-least-reproducible IntelliSense parsing issue with Omniverse Kit/Carbonite headers in the current tooling, not a defect in your extension code