VC 2003 on Vista64

  • Thread starter Thread starter Michael Sgier
  • Start date Start date
M

Michael Sgier

Hi
while trying to debug I get a message that I should be either a debug
user or admin. I'm actually in the admin group as user.
What shall I do?

Secondly where should I put the header files?

Thanks
Michael
 
Michael said:
Hi
while trying to debug I get a message that I should be either a debug
user or admin. I'm actually in the admin group as user.
What shall I do?

Secondly where should I put the header files?
Click to expand...

Michael:

VS200 is not supported on Vista, though it may well work.

On Vista it is not sufficient to be an administrator; you must run as
administrator (which will give UAC prompt on startup). You can modify the VS2003
shortcut to do this by default.

What header files do you mean?
 
Hi David
thanks I'll try as admin.
I've some cpp and h files which I want to integrate into my new VC project.
this line in a cpp file gives an error:

#include "XPLMPlugin.h"

where shall I put XPLMPlugin.h?

or where can I see/set this path in VC2003?
( years back i only did some VB.NET )
Thanks
Michael
 
Michael said:
Hi David
thanks I'll try as admin.
I've some cpp and h files which I want to integrate into my new VC project.
this line in a cpp file gives an error:

#include "XPLMPlugin.h"

where shall I put XPLMPlugin.h?
Click to expand...

Michael:

You should understand that the folder structure that you see in Solution
Explorer in Visual Studio need have no relation to the actual location on disk.

Normally, as you develop a VC project in Visual Studio, all the .h and .cpp are
put in the same directory on disk (the project directory). In that case the simple

#include "xxx.h"

will always work correctly, because the first place the compiler will look is in
the same directory as the referencing .cpp file.

What is the relationship between the .h file and .cpp file you mention in your
post? Is the former an existing file and the latter one of your files? And what
is the directory structure of the existing files?

Anyway, some possibilities:

1. Just copy your existing files into the project directory and add them to the
project in that location.

2. Keep the existing files in their current location and modify the #include
statements in your new code to use a full path or relative path.

3. Keep the existing files in their current location and add an "Additional
#include directory" to your project (Project Properties->C/C++->General.

4. Make a static library (.lib) file out of the existing files

5. Make a dynamic library (.dll) file out of the existing files
 
Back
Top