[
https://issues.apache.org/jira/browse/NPANDAY-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Corneliussen updated NPANDAY-123:
--------------------------------------
Description:
some utilities are called from within the assemblies - such as gacutil (see
item #9904) - assuming that they are on the path. However, the default
configuration for the Visual Studio application does not establish that. To
minimise configuration for new users, the application should be able to locate
the framework paths and construct full paths to such executables.
Things to be tested
* Does NPanday build pass without .NET on the PATH (just NUnit)
* Do the integration tests pass without .NET on the PATH
* Are the NPanday-DLLs targeted to CLR 2.0 (use Reflector)
Combinations to be tested
* Windows 7 64bit, .NET 2.0, .NET 3.5, .NET 4.0, VS 2010, MVN 3, trunk->trunk
* Windows 7 64bit, .NET 2.0, .NET 3.5, .NET 4.0, VS 2010, MVN 2, trunk->trunk
* XP, VS 2005 (brett)
* XP, VS 2008 (brett)
Further Todos
* Remove all the documentation about setting up the path
* Document the very first bootstrapping build (Developer Guide)
was:some utilities are called from within the assemblies - such as gacutil
(see item #9904) - assuming that they are on the path. However, the default
configuration for the Visual Studio application does not establish that. To
minimise configuration for new users, the application should be able to locate
the framework paths and construct full paths to such executables.
> PATH should not have to be set for both Visual Studio AddIn or mvn
> command-line to function
> -------------------------------------------------------------------------------------------
>
> Key: NPANDAY-123
> URL: https://issues.apache.org/jira/browse/NPANDAY-123
> Project: NPanday
> Issue Type: Bug
> Reporter: Brett Porter
> Assignee: Lars Corneliussen
> Priority: Minor
> Fix For: 1.3.1-incubating
>
>
> some utilities are called from within the assemblies - such as gacutil (see
> item #9904) - assuming that they are on the path. However, the default
> configuration for the Visual Studio application does not establish that. To
> minimise configuration for new users, the application should be able to
> locate the framework paths and construct full paths to such executables.
> Things to be tested
> * Does NPanday build pass without .NET on the PATH (just NUnit)
> * Do the integration tests pass without .NET on the PATH
> * Are the NPanday-DLLs targeted to CLR 2.0 (use Reflector)
> Combinations to be tested
> * Windows 7 64bit, .NET 2.0, .NET 3.5, .NET 4.0, VS 2010, MVN 3, trunk->trunk
> * Windows 7 64bit, .NET 2.0, .NET 3.5, .NET 4.0, VS 2010, MVN 2, trunk->trunk
> * XP, VS 2005 (brett)
> * XP, VS 2008 (brett)
> Further Todos
> * Remove all the documentation about setting up the path
> * Document the very first bootstrapping build (Developer Guide)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
