activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Work logged] (AMQNET-327) Upgrade solution to VisualStudio 2010
Date Tue, 29 May 2012 19:54:24 GMT

     [ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()}
]

Jim Gomes logged work on AMQNET-327:
------------------------------------

                Author: Jim Gomes
            Created on: 29/May/12 19:54
            Start Date: 29/May/12 19:53
    Worklog Time Spent: 2.5h 
      Work Description: Added VS2010 solution files for NMS project.

Issue Time Tracking
-------------------

            Worklog Id:     (was: 13634)
            Time Spent: 2.5h
    Remaining Estimate: 66h  (was: 72h)

> 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: 72h
>          Time Spent: 2.5h
>  Remaining Estimate: 66h
>
> 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