You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2011/04/28 23:03:03 UTC
[jira] [Created] (AMQNET-327) Upgrade solution to VisualStudio 2010
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
Fix For: 1.6.0
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: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232784#comment-13232784 ]
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: 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
[jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049514#comment-13049514 ]
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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQNET-327) Upgrade solution to VisualStudio 2010
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-327:
-----------------------------
Remaining Estimate: 72h (was: 48h)
Original Estimate: 72h (was: 48h)
> 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
> Remaining Estimate: 72h
>
> 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
[jira] [Work logged] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Eddie Fast (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030424#comment-13030424 ]
Eddie Fast commented on AMQNET-327:
-----------------------------------
I would just like to put my vote in to keep the 2008 project files around and not delete them. For those of us who have to stay behind because of outside dependencies. Thanks.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on AMQNET-327 started by Jim Gomes.
> 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
[jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-327) Upgrade solution to VisualStudio
2010
Posted by "Eddie Fast (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051392#comment-13051392 ]
Eddie Fast commented on AMQNET-327:
-----------------------------------
We currently add the NMS .csproj files to our master solution. Then we add the projects as Project References instead of DLL references, so that it easily switches between Debug and Release configs.
So the NMS libs get built everytime we do a build.
We have been hesistant to work with the binaries because of the Debug/Release switching. But I've been searching and it appears that there is a workaround (one example: http://stackoverflow.com/questions/2859572/how-to-include-the-right-reference-in-c-using-the-browser-tab )
So, we could work off the NMS binaries and then include them as DLL references using the above technique. This will require some modification of our projects, but not a big deal.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira