Visual Studio

WHS Add-in problems with VS2010

So I recently switched all my computers to Visual Studio 2010 and I am in the process of updating all of the projects to the new format and making sure everything works. Well, Visual Studio 2010 has a bug that makes it difficult to compile large projects to target anything other than "Any CPU". If you try to compile to "x86" the resources will not compile.

Visual Studio Team System, /analyze и D9040

В версиях Visual Studio Team System (в отличие от "обычных" редакций Visual Studio) в компиляторе C++ есть ключ командной строки /analyze. Этот ключ позволяет запустить модуль статического анализа, встроенный в Team System для поиска в коде некоторых ошибок.

Статический анализ в Team System можно включить не только из командной строки, но и из оболочки. Для этого в настройках C++-проекта надо выбрать вкладку Configuration Properties->C/C++->Advanced и включить "Enable Code Analysis For C/C++", как показано на рисунке.

Intel® Parallel Inspector’s Solution Explorer context menu stops working after installing Intel® Parallel Advisor Lite

When Intel® Parallel Advisor Lite is installed after Intel® Parallel Inspector Update 1 is installed, please repair Parallel Inspector installation. This is necessary to restore some Parallel Inspector GUI functionality in Visual Studio.
  • Visual Studio
  • Intel(R) Parallel Inspector
  • Intel(R) Parallel Advisor Lite
  • Parallel Computing
  • Intel Visual Fortran - fatal error LNK2023: bad DLL or entry point msobj80.dll

    For error messages: LINK: fatal error LNK2023: bad DLL or entry point 'msobj80.dll' or 'cannot find msobj80.dll' or problems with setting breakpoints in the debugger Need to move the Microsoft file msobj80.dll to a different directory
  • Microsoft Windows* (XP, Vista, 7)
  • Fortran
  • Intel® Fortran Compiler
  • Intel® Visual Fortran Composer XE
  • msobj80
  • Visual Studio
  • Visual Studio Premier Partner Edition
  • VSPPE
  • IVF
  • MSOBJDLL
  • Subscribe to Visual Studio