[
https://issues.apache.org/jira/browse/NPANDAY-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018584#comment-13018584
]
Lars Corneliussen commented on NPANDAY-123:
-------------------------------------------
Actually I think you have to do a full build with xsd and csc on the path,
before stuff works.
we should port the .net/sdk finders to java code in order to remove this
"circular" reference.
> 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
> Components: Maven Plugins
> Affects Versions: 1.2, 1.2.1
> Reporter: Brett Porter
> Assignee: Brett Porter
> 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) *worksforme
> (lars)*
> * Do the integration tests pass without .NET on the PATH *yes and no. see
> NPANDAY-393*
> * Are the NPanday-DLLs targeted to CLR 2.0 (use Reflector) *worksforme (lars)*
> Combinations to be tested
> * -Windows 7 64bit, .NET 2.0, .NET 3.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-
> * -Remove warnings about 64bit
> (http://incubator.apache.org/npanday/docs/1.3-incubating/developers/building-on-64bit.html)-
> * -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
