[ 
https://issues.apache.org/jira/browse/NPANDAY-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217829#comment-13217829
 ] 

Greg Domjan commented on NPANDAY-369:
-------------------------------------

Like to add for per project settings/defaults

It would be nice if you could default 'All configured platforms for the 
project' or otherwise specify AnyCpu/x86/x64/x86 & x64  without having to 
restart/run multiple tools due to having to run vsvars.  Some solutions may 
contain a mix of these options.  

We have needed to compile the same project using multiple MSVC versions due to 
the API.

I haven't had trouble with it yet, is it also important to be able to target 
multiple .Net Framework versions?
                
> Explicit 64bit-Support (NPanday now doesn't distinguish)
> --------------------------------------------------------
>
>                 Key: NPANDAY-369
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-369
>             Project: NPanday
>          Issue Type: Bug
>          Components: Development Setup
>    Affects Versions: 1.4-incubating
>         Environment: Win 7, x64, VS 2010 only
>            Reporter: Lars Corneliussen
>            Assignee: Lars Corneliussen
>              Labels: build, nunit, test, x64, x86
>             Fix For: 2.0
>
>
> Building NPanday from source (including tests) on 64bit windows fails.
> The problem is, that all resources are built with the 64-bit version of the 
> .NET Framework tools. Also then, the nunit-console runs everything (including 
> MSBUILD) in 64 bit.
> NPanday itself should allways be built using x86. It should furthermore have 
> strong support for building both 32bit and 64bit apps on 64bit systems.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to