kr1zz » Visual Studio

VC++ directories (include, libraries…) in Visual Studio 2010

kr1zz — Wed, 23 Feb 2011 16:14:34 +0000

In Microsoft Visual Studio 2010 VC++ directories are no longer a property of the IDE, so it is not possible to modify them from Tools->Options->Projects and Solutions->VC++Directories, it is necesary to specify them as project properties.

However, those who installed VS2010 on a box where a previous version was already installed, will find the same predefined directories. This is an annoying problem if those directories are outdated: suppose you install a newer version of some libraries (e.g. boost): then you need to remove the older one, but how?

Here’s the solution: go to $(USERPROFILE)\appdata\local\microsoft\msbuild\v4.0 and edit the profile files there (Microsoft.Cpp.Win32.user.props, in most cases).

ILOG CP optimizer: iostream.h not found?

kr1zz — Wed, 16 Feb 2011 08:29:18 +0000

I was trying IBM ILOG CP optimizer C++ API but found this error (Visual Studio 2010):

error C1083: Cannot open include file: ‘iostream.h’: No such file or directory

The error was located in ilosys.h and for a few seconds I thought I had to edit all the library .h files!!!

Fortunately I discovered it’s not necessary, simply

#define IL_STD

and things will work smoothly.

Enjoy Constraint Programming!

Unavailable Visual Studio Intellisense in C++ projetcs

kr1zz — Tue, 10 Nov 2009 10:08:10 +0000

Sometimes, in C++ projects, Visual Studio IntelliSense stops working with apparently no reasons. There are many official and non official guides on how to troubleshoot it and they almost always say that, given some conditions are respected, if IntelliSense doesn’t work, it is suggested to delete its database to let Visual Studio rebuilds it. To be able to do it, it is necessary to close the current solution, otherwise windows wouldn’t allow the access to the .ncb file.

However this procedure apparently doesn’t work for me. I have found that I also need to close the IDE and do something else. Here it follows the – at least for me – working sequence:

clean the solution
close the solution
close Visual Studio
delete the .ncb file
open Visual Studio
load the solution and clean it again
rebuild the solution

What I find particularly annoying is that after a while the buggy IntelliSense goes crazy again and I have to stop working and repeat the whole sequence again. That’s a notable waste of time!

I have reproduces this problem on some computers, with VS 2005 and 2008, and with XP and Vista, but only with unmanaged C++. I haven’t tried managed C++, while a colleague of mine says it doesn’t happen with C#.

Comments or – possibly useful – suggestions?

l’installazione di Visual Studio

kr1zz — Tue, 16 Sep 2008 13:32:38 +0000

Per installare Visual Studio 2008 su Vista c’è voluto poco più di un ora. In assoluto è un tempo lungo ma rispetto al 2005 – che come dice Edo richiede patch, service pack e palle varie – è molto poco.

Mi butto gioioso nello sviluppo

stupido visual studio!

kr1zz — Fri, 08 Feb 2008 10:55:31 +0000

Visual Studio mi fa arrabbiare perché è infido. Dopo aver passato quattro giorni a installarlo e disinstallarlo e reinstallarlo, cercando di scoprire l’ordine corretto con cui installare i vari service pack che servono, pensavo di aver risolto il problema. Invece, a distanza di qualche tempo, ecco che ricomincia a piantarsi nel bel mezzo del debug, proponendomi di reinstallarlo per risolvere il problema (una dll mancante, dice).

Che palle