IntelliSense for .cu files lack CUDA headers, defines, etc., when configured based on a custom config provider's 'browse config' (a base configuration used when a configuration is not available for a specific file).
It should work similarly to when configured by a base configuration. If not part of a full command line, and the 'compiler path' does not refer to nvcc, CUDA files should get arbitrarily reassociated with 'nvcc' instead.
IntelliSense for
.cufiles lack CUDA headers, defines, etc., when configured based on a custom config provider's 'browse config' (a base configuration used when a configuration is not available for a specific file).It should work similarly to when configured by a base configuration. If not part of a full command line, and the 'compiler path' does not refer to nvcc, CUDA files should get arbitrarily reassociated with 'nvcc' instead.