[NPANDAY-412] Execuable path for Windows 7 SDK is not auto-detected when npanday-settings.xml is generated, resgen.exe not found

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4-incubating
• Fix Version/s: 1.4-incubating
• Component/s: Maven Plugins

Environment

C:\Users\jfallows>mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
Java version: 1.6.0_24
Java home: C:\Progra~1\Java\jdk1.6.0_24\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"

• Assignee: Lars Corneliussen
• Reporter: John Robert Fallows
• Created: 19/Apr/11 22:25
• Updated: 03/May/11 07:53
• Resolved: 03/May/11 07:53

Description

The executable paths in npanday-settings.xml make it unnecessary to manually modify the command shell path for executables such as mcs.exe, xsd.exe, etc.

However, resgen.exe is also needed during the NPanday project lifecycle, but is distributed with Windows SDK rather than .Net SDK. To address this, the executable path can be updated for each vendor entry to include a reference to the Window SDK location such that resgen.exe can be found via executablePath at runtime.

When npanday-settings.xml is generated, these executablePath entries are not present, causing issues when resgen.exe cannot be located, while all the other executables can be located successfully.

See below for an example:

<?xml version="1.0" encoding="utf-8"?>
<npandaySettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <operatingSystem>Microsoft Windows NT 6.1.7600.0</operatingSystem>
  <defaultSetup>
    <vendorName>MICROSOFT</vendorName>
    <vendorVersion>2.0.50727</vendorVersion>
    <frameworkVersion>2.0.50727</frameworkVersion>
  </defaultSetup>
  <vendors>
    <vendor>
      <vendorName>MICROSOFT</vendorName>
      <vendorVersion>2.0.50727</vendorVersion>
      <frameworks>
        <framework>
          <frameworkVersion>2.0.50727</frameworkVersion>
          <installRoot>C:\Windows\Microsoft.NET\Framework64\v2.0.50727</installRoot>
          <executablePaths>
            <executablePath>C:\Program Files\\Microsoft SDKs\Windows\v6.0A\bin</executablePath>
          </executablePaths>
        </framework>
      </frameworks>
    </vendor>
...
  </vendors>
</npandaySettings>

Issue Links

• is part of: NPANDAY-123 PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function