activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <>
Subject [jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio 2010
Date Tue, 14 Jun 2011 23:30:48 GMT


Jim Gomes commented on AMQNET-327:

Hi, Eddie.  Thanks for the feedback.  I fully understand that some are unable to upgrade to
VS2010.  However, would it be too much trouble for you to use the NAnt scripts for building?
 You will still be able to perform any necessary debugging in your own project from the resulting
build output.  The only thing you won't be able to do is build from within the IDE, unless
you install the free VS2010 Express.

I guess I'm looking to find out what you won't be able to do and how much of an inconvenience
it will be.  There is a certain amount of inconvenience in maintaining multiple IDE build
projects, which are themselves redundant to the NAnt scripts.

> Upgrade solution to VisualStudio 2010
> -------------------------------------
>                 Key: AMQNET-327
>                 URL:
>             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.
For more information on JIRA, see:


View raw message