Cannot find include directory

[Peder Olav]

Hi

I just installed the evaluation version of Measurement Studio.

When I now create a new project (C++) within Visual Studio .Net 2003, I get error messages like 'Cannot open include file: "stdlib.h" ' and simular messages.
I think the installation of Measurement studio mess up some paths in Visual Studio. The include statements are generated by Visual studio itselfs, so it should be correct 😉

Does anyone now how to change the setting back to it original ?

Thanks
Peder Olav

[bilalD]

Hello

There were some reports of Measurement Studio 7.0 causing this. Check out this thread for more information.

Visual Studio .NET stores its C++ directories information in a file called VCComponents.dat.

I have attached the VCComponents.dat file for my system. It has some extra folder paths in there (for CVI and such) that you wont need so you can just remove them after the file has been loaded by Visual Studio.

You might already have a VCComponents.dat (see above link for more information about this file) in the following location:

:\Documents and Settin
gs\\local settings\Application Data\Microsoft\VisualStudio\7.1

It's probably empty, which is what is causing this problem. You can open this file with notepad to view its contents. Save the vccomponents.dat file that I have attached here to the location above and restart Visual Studio.
Or if you have another machine with Visual Studio .NET 2003 installed on it, you can copy the vccomponents.dat file from that PC as well. In this case, you would need to run the measurement studio installer again for it to add the paths correctly. Or you could have a look at the file that I have attached and add the measurement studio paths manually.

Then , if you launch Visual Studio .NET and go into Tools >> Options >> Projects >> VC++ directories, you should have all the folders show up correctly. You can remove any folders that you dont need

What was the system configuration when you installed measurement studio 7.0 eval? We have been unable to reproduce this problem in house and
if you can provide us with info about what steps you tool to get into this state, that would help us alot.

Hope this helps. Let me know if you have any questions. Thanks


Bilal Durrani
NI

[Peder Olav]

Hi.

Thanks for the quick and correct answer.
It saves a lot of time for me.
But is should not be like that, so I hope you can solve this problem.

My configuration is:
- Windows XP Pro with SP1
- Microsoft Visual Studio .Net 2003 (ent. architect)

One of my colleagues has the same configuration, and I have attached his VCComponents.dat. I read the other thread and I am quite sure he has not been into "tools->options->projects->Show Directories etc". I guess my VCComponents.dat was same, before I install Measurement Studio.

If you need more information about my system, just ask.

Good luck
Peder Olav

[bilalD]

This helps a great deal. We changed the way the Measurement Studio paths were updated in MStudio 7.1, so this should no longer be a problem.

I verified this using your VCComponents.dat file with MStudio 7.1.

Thanks for your help

Bilal

[Colin hughes]

The above seems to be the same problem that I have been getting.
Not only is MFC screwed up but also managed C++.
I have wasted many hours trying to solve some of the problems created by the installation of measurement Studio 7.
Having shipped incomplete buggy version of measurement Studio, why don't NI do the right thing and give us involuntary beta tester a free upgrade.

I have wasted many hours again last week trying to get a managed C++ project to except code in the CPP file but with silly errors.

I am OK as long as I put code in header file only and not use any standard headers.

The only clew is a warning that I get is that it cant find Libc compiled header.
Also it can not find any standard header that I might add.
I have ordered an upgrade to 7.1 but under protest that NI shipped buggy v 7 that has cost us a lot off costly down time and stalled our current project.

I have asked many times for a free upgrade that I think we are entitled to and have asked my UK rep many times for but fogged off.

I am not pleased with current money grabbing attitude from NI considering the amount of products that we purchase from you.
And no, I am not going waist any more time fixing the current unfinished (lack of user interface controls, old 2D at that ) buggy version 7
compensation for my wasted time (which is paid for by my bosses) is in order here by a free upgrade.

Colin Hughes.
Delphi Diesel Systems
UK

[Colin hughes]

After discussions with my helpful UK NI rep all my problems have been resolved.
It pays to complain some time.
Thanks NI and my UK rep Nick for there help.

Like the new formum.

Colin Hughes
Delphi Diesel systems

[Tralfaz]

I had the same problem last week [April, 2005], so it looks like the problem hasn't been fixed. Here's my system info:

Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600

MS .NET Framework 1.1 Version 1.1.4322 SP1

[bilalD]

Are you using the Measurement Studio 7.1 C++ libraries with VS.NET 2003?

[Tralfaz]

---

@bilalD wrote:
Are you using the Measurement Studio 7.1 C++ libraries with VS.NET 2003?

---

I'm not sure which version of the Measurement Studio libs I'm using; I just downloaded the eval version from the NI website. The first time I installed it, I had the problem withe the include directories and the library directories. I uninstalled Measurement studio and eventually fixed the problems so I could get Visual Studio to work on its own.

I installed the EVAL version of Measurement Studio a second time, and the include path is okay, but the library path is hosed. By "hosed" I mean that my Visual Studio projects won't link. These are pre-existing projects that don't use Meaurement Studio at all.

I was able to fix the problem by replacing my old VCComponents.dat, but it would be nice to get it working right. If this is juyst a problem with the EVAL version, it's not that big a deal since we'll be buying LabVIEW and Measurement Studio soon.

[bilalD]

The eval version that is currently available is version 7.0, so that would explain the problem. We don't provide an eval version of Measurement Studio 7.1. But this problem has been fixed in 7.1.

I apologize for the incovenience.