From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Measurement Studio for VC++

cancel
Showing results for 
Search instead for 
Did you mean: 

Intellisense does not work on Labwindows/Cvi functions in Visual C

I have used the NI Measurement Studio App. Wizard to convert one of the sample utility threaded projects in Microsoft Visual C++ 6.0. Though the intellisense is working correctly for non-labwindows related functions, like sprintf, the intellisense does not work for Labwindows related functions, like Delay, CmtDiscardThreadPool. The project compiles, links and runs with no errors. I can right-click on the Labwindows related function and select Goto definition of ... and the appropriated header file is opened.
0 Kudos
Message 1 of 2
(3,044 Views)
This is a known issue with Intellisense support in Visual C++. Intellisense in Visual C++ is provided by .NCB files. Microsoft ships three pre-built Intellisense database stores for Visual C++ 6.0 - CRT.NCB for the Visual C++ runtime (hence why you see sprintf working), MFCATL.NCB for the MFC and ATL libraries, and WIN32.NCB for the Win32 API. Microsoft currently does not provide a way for third parties to install pre-built stores that function the way that these do.

The only other way to get Intellisense in your project is to add the header files for the libraries that you're using to your project. The Measurement Studio wizard can do this intelligently for the Measurement Studio for Visual C++ libraries because the libraries are componentized and the
wizard has ways to determine exactly which headers are associated with a given component. The wizard does not add CVI headers to the project for Intellisense when converting a CVI project to a Visual C++ project, and this is why you aren't seeing Intellisense for the CVI functions. If you want Intellisense for the CVI functions, you'll have to add the appropriate CVI headers to your project.

- Elton
Message 2 of 2
(3,044 Views)