activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio 2010
Date Mon, 19 Mar 2012 18:09:38 GMT


Jim Gomes commented on AMQNET-327:

I've had to create a custom build tool around working with .NET assemblies to copy in the
debug or release versions of the dependent assemblies in a just-in-time fashion during builds.
 Initially, this seemed like a major shortcoming of the compiler tools, but it actually led
to an unintended consequence of allowing a declarative project dependency model that offered
a lot of benefits.  Our custom build tool is influenced by the method used in the NMS NAnt
scripts and by Maven.  However, it doesn't tie us to any particular compiler tool, and fully
supports MSBuild (including 2008, 2010, and soon VS11), NAnt, Ant, Maven, or whatever.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message