IncrediBuild v3.61 - Release Notes

This document contains the IncrediBuild version history, as well as a list of known issues for the current version. For the most up-to-date knowledge base of known issues and articles, visit the knowledgebase section in our Support Center.

Table of Contents

Version History

Known Issues

  1. Screen saver detection is problematic on some versions of Windows NT
  2. IncrediBuild menus in the Microsoft Visual C++ 6.0 IDE may collide with third-party MSVC add-ins such as BoundsChecker, TrueTime and TrueCoverage.
  3. Changes in project settings do not trigger rebuild of affected files
  4. Preprocessor references to files are parsed when in the scope of #ifdef statements
  5. Agent service may fail to start on some versions of Windows NT (rare)
  6. Some localized versions of MSVC 6.0 may crash when opening VC with the IncrediBuild add-in installed
  7. BSCMake may fail with a "Permission denied" error when building from outside MSVC's IDE while the project is open in MSVC.
  8. In some configurations, the mouse wheel will fail to function when used from the MSVC IDE, if the IncrediBuild add-in is installed.
  9. MSVC will incorrectly determine object files are out of date after an IncrediBuild rebuild operation is run directly following a change in project-level compilation settings.
  10. When encountering an #include directive containing a preprocessor symbol that translates to the include header filename, IncrediBuild will not check that file in the dependency evaluation.
  11. When preprocessor symbols are used within #include or #import statements, IncrediBuild does not add the translated symbol to the dependency list.
  12. /Tp (compile source file as cpp regardless of extension) switch isn't supported.
  13. Keyboard shortcuts for MSVC .NET addin must be manually set after installation.
  14. After an IncrediBuild uninstall, the MSVC 7.0 addin isn't automatically removed from IDE.
  15. MSVC 7.0 toolbar buttons sometimes do not change their state according to current build status.
  16. When building renamed project files in MSVC .NET, the original project file name appears in the build output and in the Build monitor Projects view.
  17. The add-in's menu and toolbar sometimes disappear from the MSVC .NET IDE.
  18. Auto-hide feature sometimes fails with docked Build Monitor window in VS .NET.
  19. When a multi-monitor setup is used, or on systems where pcAnywhere or similar is used, IncrediBuild might display a popup reporting an "Access Violation, read of address 00000004".

Version History

Changes in Version 3.61

Visual Studio 2010 Build System

Visual Studio 2003/2005/2008 Build System

Xoreax Grid Engine (XGE) Interfaces

Stability

User Interface

Virtual Environment

Back to top


Changes in Version 3.60

Note: This list also contains changes included in Version 3.60 Beta and Version 3.60 Beta 2. For a list of differences between v3.60 and v3.60 Beta 2, see this section.

Version Highlights

Visual Studio Build System

Performance

Stability

User Interface

Virtualization

Miscellaneous

Visual Studio Integration

Xoreax Grid Engine (XGE) Interfaces

Known Issues (Visual Studio 2010)

Back to top


Differences Between v3.60 & v3.60 Beta 2

Visual Studio Build System

Visual Studio Integration

Stability

User Interface

Virtualization

Xoreax Grid Engine (XGE) Interfaces

Known Issues (Visual Studio 2010)

Changes in Version 3.60 Beta 2

New Features

Miscellaneous

Visual Studio Build System

Stability

Back to top


Changes in Version 3.60 Beta

Performance

Stability

User Interface

Virtualization

Visual Studio Build System

Visual Studio Integration

Xoreax Grid Engine (XGE) Interfaces

Miscellaneous

Back to top


Changes in Version 3.51

Visual Studio Build System

Performance

User Interface

Stability

Virtualization

Xoreax Grid Engine (XGE) Interfaces

Miscellaneous

Back to top


Changes in Version 3.50

Note: This list also contains changes included in Version 3.50 RC and Version 3.50 Beta. For a list of differences between v3.50 and v3.50RC, see this section.

Performance

Virtualization

Xoreax Grid Engine (XGE) Interfaces

Stability

User Interface

Visual Studio Build System

Miscellaneous

Visual Studio Integration

Back to top


Differences from v3.50 RC

Performance

Stability

New Features

Xoreax Grid Engine (XGE) Interfaces

User Interface

Virtualization

Visual Studio Build System

Miscellaneous

Back to top


Changes in Version 3.50 Release Candidate

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

Miscellaneous

Stability

Virtualization

User Interface

Visual Studio Integration

Back to top


Changes in Version 3.50 Beta

Stability

Performance

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

New Features

User Interface

Virtualization

Miscellaneous

Back to top


Changes in Version 3.40

Note: This list also contains changes included in Version 3.40 RC1 and Version 3.40 Beta. For a list of differences between v3.40 and v3.40RC1, see this section.

Performance

New Features

User Interface

Stability

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

Visual Studio Integration

Miscellaneous

Differences from v3.40 RC1

Back to top


Changes in Version 3.40 Release Candidate 1

User Interface

Stability

Performance

Visual Studio Build System

Visual Studio Integration

Miscellaneous

Back to top


Changes in Version 3.40 Beta

Performance

New Features

Stability

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

User Interface

Visual Studio Integration

Miscellaneous

Back to top


Changes in Version 3.32

Note: This list also contains changes included in Version 3.32 RC2 and Version 3.32 RC1. For a list of differences between v3.32 and v3.32RC2, see this section.

New Features

Xoreax Grid Engine (XGE) Interfaces

Visual Studio Build System

Stability

Performance

User Interface

Visual Studio Integration

Miscellaneous

Differences from v3.32 RC2

Items listed in this section are also listed above.

Back to top


Changes in Version 3.32 RC2

New Features

Xoreax Grid Engine (XGE) Interfaces

Visual Studio Build System

Stability

User Interface

Visual Studio Integration

Back to top


Changes in Version 3.32 RC1

Visual Studio Build System

Visual Studio Integration

Xoreax Grid Engine (XGE) Interfaces

Performance

Stability

User Interface

Miscellaneous

Back to top


Changes in Version 3.31

Changes in Version 3.30

Note: This list also contains changes included in Version 3.30 Beta.

Differences from v3.30 Beta

Performance

New Features

Stability

Miscellaneous

User Interface

Xoreax Grid Engine (XGE) Interfaces

Visual Studio Build System

Back to top


Changes in Version 3.30 Beta

Performance

New Features

Stability

Miscellaneous

User Interface

Xoreax Grid Engine (XGE) Interfaces

Visual Studio Build System

Back to top


Changes in Version 3.20

Note: This list also contains changes included in Version 3.13 Beta.

New Features

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

Miscellaneous

Back to top


Changes in Version 3.13 Beta

New Features

Visual Studio Build System

Xoreax Grid Engine (XGE) Interfaces

Miscellaneous

Back to top


Changes in Version 3.10

Note: This list also contains changes included in preceding beta versions.

Performance

Xoreax Grid Engine Interfaces

Visual Studio Build System

Miscellaneous

User Interface

Back to top


Changes in Version 3.04 Beta

Xoreax Grid Engine Interfaces

Visual Studio

Miscellaneous

Back to top


Changes in Version 3.03 Beta

Back to top


Changes in Version 3.02 Beta

Xoreax Grid Engine Interfaces

Performance

Miscellaneous

User Interface

Visual Studio Build System

Back to top


Changes in Version 3.01

Xoreax Grid Engine

Performance

General

User Interface

Visual Studio Build System

Back to top


Changes in Version 3.00 Beta

Xoreax Grid Engine

Performance

General

User Interface

Visual Studio Build System

Back to top


Changes in Version 2.61

User Interface

Performance

Build System

Other

Back to top


Changes in Version 2.60

User Interface

Build System

Other

Back to top


Changes in Version 2.50

Back to top


Changes in Version 2.50 Release Candidate 2

Performance

Build System

User Interface

Other

Back to top


Changes in Version 2.50 Release Candidate

Build System

Performance

Stability

User Interface

Visual Studio integration

Other

Back to top


Changes in Version 2.42

Back to top


Changes in Version 2.41

Build System

User Interface

Other

Back to top


Changes in Version 2.40

New Virtual Environment Module

The major change in version 2.40 is a completely re-written VE (Virtual Environment) module. The VE is responsible for remote/local compiler execution and for file caching. The effects of this change are:

Build System

User Interface

Other

Back to top


Changes in Version 2.30

Build System

User Interface

Back to top


Changes in Version 2.21

Build System

User Interface

Other

Back to top


Changes in Version 2.20

Build System

User Interface

Other

Back to top


Changes in Version 2.12

Build System

User Interface

Other

Back to top


Changes in Version 2.11

Back to top


Changes in Version 2.1

Build System

User Interface

Other

Back to top


Changes in Version 2.04

Build System

User Interface

Other

Back to top


Changes in Version 2.03

Changes in Version 2.02

Back to top

Changes in Version 2.01

Back to top


Changes in Version 2.00

Build System

User Interface

Other

Back to top


Changes in Version 1.31

Build System

User Interface

Other

Back to top


Changes in Version 1.3

Build System

User Interface

Other

Back to top


Changes in Version 1.21

Build System

User Interface

Other

Back to top


Changes in Version 1.2 Beta

Build System

User Interface

Other

Back to top


Changes in Version 1.14

Build System

User Interface

Other

Back to top


Changes in Version 1.133

Back to top


Changes in Version 1.131

Back to top


Changes in Version 1.13

Build System

User Interface

Other

Back to top


Changes in Version 1.12

Build System

User Interface

Other

Back to top


Changes for Version 1.11

Build System

User Interface

Other

Back to top



Known Issues

Screensaver detection is problematic on some versions of Windows NT

Symptom 1: Computer is unusually unresponsive, even when Agent is disabled.

Symptom 2: The Task Manager displays the process "cl.exe" as running, even when the Agent is disabled and no build is running locally.

Description: On some versions of Windows NT, the operating system falsely reports that the screensaver is currently running, due to Windows bug. As a result, the Agent process will always operate as a high-priority process, resulting in a general system slowdown. Furthermore, if the "Enable Agent while screen-saver is running" Agent option is turned on, the Agent will always participate in distributed builds, even when disabled.

Solution/workaround: Open the Agent Settings dialog. IncrediBuild will automatically notify you of this condition and switch off all screen-saver related options.
Back to top


IncrediBuild menus in the Microsoft Visual C++ 6.0 IDE may collide with third-party MSVC add-ins such as BoundsChecker, TrueTime and TrueCoverage.

Symptom: After Installing IncrediBuild, menus for these applications do not appear.

Description: This is an open bug.

Solution/workaround: Upon identifying the symptom in a machine, follow the following process:

   1. Make sure only one MSVC window is open.
   2. Select 'Customize' from MSVC's 'Tools' menu.
   3. In the 'Commands' page, select 'Menus' from the 'Category' listbox.
   4. Locate the tool's menu (for example: 'BoundsChecker') in the 'Commands' listbox, and drag-and-drop it back into the main IDE menu bar.
   5. Repeat step 4 for any other missing menus.
   6. Close the dialog, then close MSVC to save changes.

Note that it is possible to run the Setup application without installing an IncrediBuild menu in MSVC. To do this, run the Setup application with the command line switch "/nomenu". This will only install the IncrediBuild toolbar.
Back to top


Changes in project settings do not trigger rebuild of affected files

Symptom: After changing the C/C++ project settings for a project or file, IncrediBuild will not prompt to rebuild the affected files when running an incremental build.

Description: This is a know issue.

Solution/workaround: Rebuild the entire project.
Back to top


Preprocessor references to files are parsed when in the scope of #ifdef statements

Symptom 1: The IncrediBuild warning "import directives in the precompiled header should use the no_implementation attribute. See FAQ section in documentation for more details." Is received, relating to code inside a multi-line comment.

Symptom 2: When changing a file referenced by an #include statement that appears in the scope of an #ifdef statement that does not evaluate to TRUE, running an incremental build will result in the referencing file being recompiled.

Description: IncrediBuild currently parses all preprocessor references to files, including conditional (#ifdef) portions of the source. The warning described in symptom #1 can occur in cases where an #import statement appears inside such a portion. Note that if your code includes large portions of #include statements in an #ifdef portion, deleting these lines may slightly improve compilation speed.

Solution/Workaround: To make the warning in symptom #1 disappear, add the "no_implementation" keyword to the #import statement or simply delete that line.
Back to top


Agent service may fail to start on some versions of Windows NT (rare)

Symptom: When starting the Agent service, a pop-up message box saying "The service terminated unexpectedly" appears, and the service does not start.

Description: This is a known issue that appears very rarely.

Solution/workaround: In regedit, open the registry path "HKEY_LOCAL_MACHINE\SOFTWARE\Xoreax\IncrediBuild\BuildService" and change the string value "perfData" to 0. This will allow the Agent to start and initiate builds, although the Agent will not participate in remote builds.
Back to top


Some localized versions of MSVC 6.0 may crash when opening VC with the IncrediBuild add-in installed

Symptom: When starting MSVC with the IncrediBuild add-in installed, MSVC warns about not being able to define keyboard shortcuts. Keyboard shortcuts for IncrediBuild commands are not available after this.

Description: This is a known issue that has to do with keyboard shortcut definition in localized versions of MSVC.

Solution/workaround: Notify Xoreax support of this. Mention what MSVC language version you are using. The workaround for this problem is as follows:

   1. Close all MSVC windows.
   2. Open the Agent Settings dialog "Microsoft Visual Studio" page.
   3. Select "Visual Studio 6.0" in the "Add-in installation/removal" box.
   3. Press the "Remove Add-in" button.
   4. Uncheck the "Create Keyboard shortcuts on Add-in initialization" checkbox.
   5. Press the "Install Add-in" button.
   6. Open MSVC 6.0.
   7. Manually define keyboard shortcuts to IncrediBuild commands by following this procedure:
      a. Open the Tools->Customize menu command.
      b. Switch to the "Keyboard" page.
      c. Choose the "Add-ins" category.
      d. Assign keyboard shortcuts to the different commands. Note that the default IncrediBuild keyboard shortcuts are:
         i. IncrediBuild_Build - Shift+F7
         ii. IncrediBuild_OpenMonitor - Shift+F8
         iii. IncrediBuild_Stop - Shift+Pause
Back to top


BSCMake may fail with a "Permission denied" error when building from outside MSVC's IDE while the project is open in MSVC.

Symptom: Build fails with the error "BSCMAKE: error BK1506 : cannot open file X.bsc': Permission denied" when building from the tray-icon menu or with BuildConsole while the project is open in MSVC.

Description: This is a known issue.

Solution/workaround: Either close the workspace in MSVC or build from the IDE.
Back to top


In some configurations, the mouse wheel will fail to function when used from the MSVC IDE, if the IncrediBuild add-in is installed.

Symptom: Mouse wheel does not function when used within MSVC. Removing the IncrediBuild add-in for MSVC restores normal operation.

Description: This is a known issue that will be fixed in a future release.

Solution/workaround: In most cases, installing the latest mouse driver from the Internet fixes the problem.
Back to top


MSVC will incorrectly determine object files are out of date after an IncrediBuild rebuild operation is run directly following a change in project-level compilation settings.

Symptom: Pressing F7 or F5 after the above condition was met will result in a 'files out of date' message box, even though intermediate and output files are up-to-date.

Description: This is a known issue that may be fixed in a future release.

Solution/workaround: To prevent this from occurring, start a VC build after changing project-level compilation settings, stop it, then continue with an IncrediBuild incremental build. Note that closing and re-opening the project in the IDE will make MSVC realize that the files are up-to-date.
Back to top


When encountering an #include directive containing a preprocessor symbol that translates to the include header filename, IncrediBuild will not check that file in the dependency evaluation.

Symptom: When the above is true, modifying that header file will not result in IncrediBuild rebuilding the including source file as a result of the changes.

Description: This is a known issue that may be fixed in a future release.

Solution/workaround: Use explicit file paths in source files.
Back to top


When preprocessor symbols are used within #include or #import statements, IncrediBuild does not add the translated symbol to the dependency list.

Symptom: When a preprocessor symbol is used inside these statements (for example: #include __MYFILENAME ) the translated filename will not be considered when dependencies are calculated for that file.

Description: This is a known issue that will be fixed in a future release.

Solution/workaround:There is no current workaround.
Back to top


/Tp (compile source file as cpp regardless of extension) switch isn't supported.

Symptom: When the /Tp compiler command line switch is used, the compiler will generate a command line error message.

Description: This is a known issue that may be fixed in a future release.

Solution/workaround:Use the /TP switch (identical in functionality) instead of the /Tp switch.
Back to top


Keyboard shortcuts for MSVC .NET addin must be manually set after installation.

Symptom: After installation, no keyboard shortcuts are set for IncrediBuild operations.

Description: This is a known issue caused by MSVC 7.0's inability to predefine keyboard shortcuts for custom addins.

Solution/workaround: Manually define keyboard shortcuts for each operation using the following procedure:
   1. From the IDE, choose "Tools->Customize...".
   2. Press the "Keyboard..." Button.
   3. In the "Show commands containing:" text box, enter "BuildAddInVC7".
   3. Use the dialog's controls to add keyboard shortcuts for each IncrediBuild command.
Back to top


After an IncrediBuild uninstall, the MSVC .NET addin isn't automatically removed from IDE.

Symptom: The IncrediBuild toolbar and menu still appear in the IDE after removing the IncrediBuild installation.

Description: This is a known issue caused by MSVC 7.0's inability to automatically remove addins from the IDE.

Solution/workaround: After running the IncrediBuild uninstall, close all MSDEV 7.0 windows and run the command "DevEnv /setup" to finish the uninstall process.
Back to top


MSVC 7.0 toolbar buttons sometimes do not change their state according to current build status.

Symptom: The toolbar buttons will sometimes not become disabled/enabled immediately after stopping or starting a build from the addin.

Description: This is a known issue caused by an MSVC 7.0 bug.

Solution/workaround: To refresh the buttons' state, click any window inside the IDE.
Back to top


When building renamed project files in MSVC .NET, the original project file name appears in the build output and in the Build monitor Projects view.

Description: This is a known issue that will be fixed in a future release.

Solution/workaround: There is no current workaround.
Back to top


The add-in's menu and toolbar sometimes disappear from the MSVC .NET IDE.

Symptom: MSVC opens up with no IncrediBuild menu or toolbar, despite having run the setup and enabled MSVC .NET IDE integration.

Description: This is a known issue.

Solution/workaround: Use the Agent Settings dialog "Microsoft Visual Studio" page to restore the add-in.
Back to top


Auto-hide feature sometimes fails with docked Build Monitor window in VS .NET.

Symptom: IncrediBuild docked Build Monitor doesn't automatically open when starting a new build in VS .NET.

Description: This is a known issue related to Visual Studio 2005's plug-in architecture.

Solution/workaround: Click 'Hide Monitor' and then 'Show Monitor' to show the Build Monitor.
Back to top


When a multi-monitor setup is used, or on systems where pcAnywhere or similar is used, IncrediBuild might display a popup reporting an "Access Violation, read of address 00000004".

Description: This is a known issue.

Solution/workaround: Restart the IncrediBuild application that displayed this message.
Back to top


Copyright (C) 2001-2011 Xoreax Software Ltd. All rights reserved.
Converted from CHM to HTML with chm2web Standard 2.85 (unicode)