Products, the Universe and Everything

The Riverblade Developer's Blog

Beth demonstrating Visual Lint at the ACCU Conference 2008  Anna taking part in a discussion panel at the European Software Conference 2007 

Welcome to our developer's blog. We hope that this forum provides an insight into us, our products and how we develop them. Please feel free to write to us if you have anything to add to any of the posts here.

Current Entries | Archives |


LintProject Pro 2.0.10.19 has been released
Thursday, August 26, 2010

The following changes are included in this build:
  • Corrected the parsing of RuntimeLibrary definitions in Visual C++ 2010 project (.vcxproj) files [VS2010] [from Visual Lint 2.5.4.136].

  • Speeded up the parsing of Visual Studio 2010 C++ project (.vcxproj) files further [VS2010] [from Visual Lint 2.5.4.136].

  • When a Visual C++ 2010 project (.vcxproj) file is parsed, the contents of each configuration are no longer read automatically. Instead, they are loaded on demand when the contents of the configuration is requested, which can significantly speed up the loading of complex projects [VS2010] [from Visual Lint 2.5.4.136].

  • Corrected the analysis results parser to strip leading and trailing whitespace from source file pathnames [also in Visual Lint 2.5.4.136].

  • Added support for the Visual C++ CL environment variable. Any compiler options contained in this variable will now be reflected in the contents of project indirect files [VS2002-VS2010] [from Visual Lint 2.5.4.136].

  • Added support for forced include project properties in Visual C++ 2002-2010 project (.vcproj and .vcxproj) files [VS2002-VS2010] [from Visual Lint 2.5.4.136].

  • Desensitised the Visual C++ project (.vcproj) file parser to doubled path delimiters in folder paths used to load inherited property sheet (.vsprops) files [VS2002-VS2008] [from Visual Lint 2.5.4.136].

  • The operating system version information written to the application logfile now includes the name of the OS rather than just the OS version number [from Visual Lint 2.5.4.136].

  • Corrected the analysis results parser to strip leading and trailing whitespace from source file pathnames [from Visual Lint 2.5.4.136].


Posted by Anna at 10:51 | Get Link

 

Visual Lint 2.5.4.136 has been released
Wednesday, August 25, 2010

The following changes are included in this build:
  • When a Visual C++ 2010 project (.vcxproj) file is parsed, the contents of each configuration are no longer read automatically. Instead, they are loaded on demand when the contents of the configuration is requested, which can significantly speed up the loading of complex projects [VS2010].

  • Corrected the analysis results parser to strip leading and trailing whitespace from source file pathnames.

  • Added support for the Visual C++ CL environment variable. Any compiler options contained in this variable will now be reflected in the contents of project indirect files [VS2002-VS2010].

  • Added support for the Visual C++ INCLUDE environment variable. If Visual Studio is invoked with the /UseEnv option, the contents of this variable will be written by Visual Lint Enterprise Edition as -i directives to all new project indirect files. Note that for this to work correctly, a custom std.lnt file which does NOT specify the global include folder configuration must be used for the solution concerned [VS2002-VS2010] [Visual Lint Enterprise Edition].

  • Added support for forced include project properties in Visual C++ 2002-2010 project (.vcproj and .vcxproj) files [VS2002-VS2010].

  • Desensitised the Visual C++ project (.vcproj) file parser to doubled path delimiters in folder paths used to load inherited property sheet (.vsprops) files [VS2002-VS2008].

  • The operating system version information written to the Status View now includes the name of the OS rather than just the OS version number.

  • Fixed issues in the parsing of RuntimeLibrary properties within Visual C++ 2010 (.vcxproj) project files [VS2010].

  • Revised the project loading sequence to avoid reading project files a second time to generate project indirect files. Note that this optimisation has an effect only when a new project indirect file needs to be written.


Posted by Anna at 10:51 | Get Link