activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Commented) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio 2010
Date Fri, 13 Apr 2012 13:25:22 GMT

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

Timothy Bish commented on AMQNET-327:
-------------------------------------

Jim, I'd say go ahead and migrate the project to VS2010.  The project files are redundant
on the NAnt scripts for build purposes and are really a convenience for the dev team, the
binaries are the end product so whatever makes us more productive in creating new NMS releases
is best.  
                
> Upgrade solution to VisualStudio 2010
> -------------------------------------
>
>                 Key: AMQNET-327
>                 URL: https://issues.apache.org/jira/browse/AMQNET-327
>             Project: ActiveMQ .Net
>          Issue Type: Task
>          Components: ActiveMQ, EMS, MSMQ, NMS, Stomp, WCF
>            Reporter: Jim Gomes
>            Assignee: Jim Gomes
>              Labels: net-2.0, net-3.5, net-4.0, vs2010
>             Fix For: 1.6.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The solution files should be upgraded to VisualStudio 2010.  At the same time, now projects
will be created to target specific .NET versions.  The existing projects will be renamed to
XXX-net2.0.csproj or XXX-net3.5.csproj, as appropriate.  For example, the vs2008-nms.csproj
will be renamed to vs2010-nms-net2.0.csproj.  It will then be duplicated to vs2010-nms-net4.0.csproj
to target the .NET 4.0 framework.  Other platform specific versions can be created on an as-needed
basis.  These individual project files will all be included in the single vs2010-nms.sln file.

--
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

        

Mime
View raw message