looking up definitions in Visual Studio

Hi Juergen, I think if you are using VS Express it doesn't support add-ins, so vAssistX isn't an option.

Ian

Thanks for all your help.
Eugenio, adding those .rsp paths as additional include dirs and compiling helped VS to find the declarations. That's quite good now.

Thanks Ian for your tip. Making use of the standard stuff is sufficient for now. I'm still about to see if ID plugin development is the right thing for me and I'm using VS Express Edition. So I think vAssistX would be overkill for now.

Juergen

If you are doing significant development with VS I would suggest a look at visual assist x - see www.wholetomato.com. Like Dirk, I used to prefer CodeWarrior, but now I would say VS with vAssistX. Don't be put off by the site name - I was at first. FYI - I have no association with the product at all, just a user.

Ian

Hallo Juergen,

The projects created with Dolly and most example projects use a special file that specifies a lot of include paths via an additional command line option. This works for compiling, as the compiler will find the included files, but it does not work very well in the IDE. This file is usually something like "xxxCPP.rsp"

What you need to do is to add all the include paths listed in the "xxxCPP.rsp" file to the project configuration, under "Configuration Properties" | "C/C++" | "General" | "Additional Include Directories".

Once you have changed this and have successfully built the project at least once in debug mode with browse information activated, VS should find most symbols and also the included files.

Regards,
Eugenio Andres - http://www.expertosinformaticos.com

I'd guess that VS does not search the include paths specified via .rsp files - XCode has a similar problem with .xcconfig files. Another suspect would be $VARIABLE substitutions within the paths.

It won't help you, but my choice for writing larger sources is still CodeWarrior.

Dirk