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 |


Visual Lint for Windows 7
Tuesday, May 19, 2009

Hi there, my name is Beth Mackenzie. I've been rather overdue in introducing myself to you, but I hope to rectify that now. Among other things, I'm responsible for much of our testing as well as research into possible support for new IDEs (I've recently been working with Visual Studio 2010, CodeGear 2009 and Embedded IDE's such as Code Composer Studio 3.x/4 to name but a few) and Operating Systems. It's the latter I wish to talk about today - and Windows 7 in particular.

We have actually been testing with Windows 7 for several months, and in fact the grid computing demonstrator we recently showed at the ACCU Conference used a pair of Q9550 quad core machines running the Windows 7 Beta.

When a new operating system becomes available to developers, we usually run our normal tests to catch any breaking changes. In this case, the test's aim was to make sure Visual Lint will run with Visual Studio 2008 on Windows 7, i.e. to ensure that the application installs and executes as it should.

If you haven't seen it, Windows 7 displays its pulsating logo which appears in the center of the screen, it's an atomic aesthic just right for the Hadron collider age that we all live in:



Windows 7 has a nice smooth user interface layer, less clutter, an uncluttered install sequence like Windows 2008 Server. Here is my screen shot installing the development build of Visual Lint:



So far so good.

And here is my screen shot of Windows 7 using Visual Studio 2008 running the development build of Visual Lint:



I think it's worth the mention that we used installed Windows 7 on both Quad-core test machines for the ACCU Conference 2009 that we recently attended in Oxford. Anna has been blogging enthusiastically about our time at the conference.

I plan to upload a running movie of Visual Lint in Windows 7, but i'd better continuing testing the latest build!

We tested with the Windows 7 Beta here, and of course will we shortly be retesting with recently release.

You can find me writing regular product updates through Twitter
~Beth Mackenzie

Posted by Beth at 09:19 | Get Link

 

LintProject Professional 2.0.2.10 has been released
Monday, May 18, 2009

The changes in this build include:
  • PC-lint raw analysis results generated without an env-vc*.lnt environment file can now be parsed correctly. Also improved the handling of messages in the module wrap-up [from Visual Lint 2.0.6.111a].

  • Wildcards can now be used to exclude both files and projects from analysis.

  • Corrected an issue with relative paths in the handling of the PC-lint std.lnt indirect file.

  • Empty projects are now no longer shown with "Pending" status in the solution report.

  • Removed the "Uninstall..." shortcut from the Start Menu (as per current guidelines the Control Panel "Add/Remove Programs" applet should be used instead).

  • Revised the way command line swiches are parsed. As a result, a delimiter ('=' or ':') should now be used with switches (e.g. /configfile) which have following parameters.

  • When a Visual C++ project file containing comma delimited preprocessor definitions (the IDE uses semicolons) is read, the corresponding definitions in generated project.lnt file will now be correctly semicolon delimited (this fixes an analysis error when definitions of the form SYMNAME=, are encountered in the project.lnt file) [from Visual Lint 2.0.4.107].

  • Corrected the category totals and sort order in the "Issue Count by Project" section of the HTML solution report template [from Visual Lint 2.0.4.107].

  • If exception handling (/GX) is enabled in a Visual C++ project, _CPPUNWIND will now automatically be defined in generated project.lnt files [from Visual Lint 2.0.5.109].

  • Charts generated as part of HTML reports are now saved as .bmp and then converted to .png using GDIplus, as the lpng.dll used by TeeChart8.ocx to perform this function natively seems to have issues with DEP on Windows Server 2008 and Windows Vista [from Visual Lint 2.0.5.109].

  • Fixed a bug in the project indirect file writer which could cause paths such as "..\..\Folder" to be incorrectly resolved [from Visual Lint 2.0.6.111].

  • Fixed a bug which would cause a crash if a project file containing files of the form "\\filename.ext" was encountered [from Visual Lint 2.0.6.111].

  • Fixed a bug in the project indirect file writer which could cause paths such as "Folder1\Folder2\..\Folder3" to be incorrectly resolved [from Visual Lint 2.0.6.111].

  • Added support for Visual Studio variable $(WebDeployPath) in .vcproj files [from Visual Lint 2.0.6.111].

  • Corrected a bug in the Analysis Results parser which could cause a reference line in a specific walk to be parsed as a lint message - leading to an erroneous fatal error [from Visual Lint 2.0.6.111].

  • Added support for "AdditionalOptions" within inherited property sheet (.vsprops) files [VS2002 onwards] [from Visual Lint 2.0.6.111].

  • Guarded against malformed -i directives (e.g. /I"Path) in Visual C++ response files [from Visual Lint 2.0.6.111].

  • Corrected the handling of .vsprops files whose location is defined via configuration specific Visual Studio environment files (e.g. "$(SolutionDir) Common_Sources\Win\CompileOptions\$(ConfigurationName)Plugin.vsprops") [from Visual Lint 2.0.6.111].

  • Project configurations which inherit Intermediate and Output Directory values within .vsprops files are noware now correctly handled [VS2002 onwards] [from Visual Lint 2.0.6.111].

  • Improved error handling when an unsupported solution, workspace or project file type is specified.

Posted by Anna at 09:45 | Get Link

 

Visual Lint 2.0.6.111 has been released
Tuesday, May 12, 2009

The following changes are included in this version:
  • Fixed a bug in the project indirect file writer which could cause paths such as "..\..\Folder" to be incorrectly resolved.

  • Fixed a bug in the project indirect file writer which could cause paths such as "Folder1\Folder2\..\Folder3" to be incorrectly resolved.

  • Fixed a bug which would cause a crash if a project file containing files of the form "\\filename.ext" was encountered.

  • Added support for the Visual Studio variable $(WebDeployPath) in .vcproj files.

  • Corrected a bug in the Analysis Results parser which could cause a reference line in a specific walk to be parsed as a lint message - leading to an erroneous fatal error in the analysis results.

  • Added support for "AdditionalOptions" within inherited property sheet (.vsprops) files [VS2002 onwards].

  • Fixed a bug in the parsing of analysis results returned by IncrediBuild [Visual Lint Enterprise Edition].

  • Corrected a bug in the Analysis Results Display which caused the "Categories" control to be configured incorrectly on start-up [Visual Lint Standard and Professional Editions].

  • The "Auto-select project" option in the Analysis Status Display is now persistent. In addition, if this option is active when a solution is loaded the display will now automatically reflect the contents of the active window.

  • The "View" control in the Analysis Results Display is now persistent.

  • Version information for IncrediBuild is now only shown in the "Visual Lint Status" pane in the Output Window if the active product edition is Visual Lint Enterprise Edition.

  • The default subject text in email enquires from the About Box now includes details of the active product edition.

  • Added support for additional command line options of the form -I "folder path" within Visual C++ project files.

  • Guarded where possible against malformed -i directives (e.g. /I"Path) in Visual C++ response files.

  • Corrected the handling of .vsprops files whose location is defined via configuration specific Visual Studio environment files (e.g. "$(SolutionDir)Common_Sources\Win\CompileOptions\$(ConfigurationName)Plugin.vsprops").

  • Project configurations which inherit Intermediate and Output Directory values within .vsprops files are now correctly handled [VS2002 onwards].

  • Corrected a potential deadlock in the interactions between the "Delete Analysis Results" command and the IncrediBuild task scheduler [Visual Lint Enterprise Edition].

  • Re-themed the installer and Configuration Wizard.


Posted by Anna at 10:48 | Get Link