You are viewing a plain text version of this content. The canonical link for it is here.

Posted to npanday-dev@incubator.apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2014/08/04 06:17:11 UTC

[jira] [Closed] (NPANDAY-393) NPanday ITs still need ildasm (or disasm for Mono) to be on the PATH

     [ https://issues.apache.org/jira/browse/NPANDAY-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed NPANDAY-393.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Backlog)
                   1.5.0-incubating
         Assignee: Brett Porter

Addressed in r1609664

> NPanday ITs still need ildasm (or disasm for Mono) to be on the PATH
> --------------------------------------------------------------------
>
>                 Key: NPANDAY-393
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-393
>             Project: NPanday
>          Issue Type: Improvement
>          Components: Integration Tests
>            Reporter: Lars Corneliussen
>            Assignee: Brett Porter
>              Labels: integration-tests
>             Fix For: 1.5.0-incubating
>
>
> As NPanday doesn't need the PATH environment setup anymore, it would be great, if the ITs ran without that, too. Instead some ITs expect ildasm or disasm to be available in the executing command line environment.
> Workaround: Run ITs in the SDK or Visual Studio Prompt.



--
This message was sent by Atlassian JIRA
(v6.2#6252)