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 2009/11/10 21:17:52 UTC
[jira] Resolved: (AMQNET-209) Add extension methods to improve the
readability of the SessionUtils and XmlUtils functions.
[ https://issues.apache.org/activemq/browse/AMQNET-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-209.
------------------------------
Resolution: Fixed
> Add extension methods to improve the readability of the SessionUtils and XmlUtils functions.
> --------------------------------------------------------------------------------------------
>
> Key: AMQNET-209
> URL: https://issues.apache.org/activemq/browse/AMQNET-209
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: NMS
> Affects Versions: 1.1.0
> Environment: .NET 3.5, MONO
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.2.0
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> .NET 3.5 and MONO support extension methods. Extension methods, if used carefully, can seamlessly extend the API in a type-safe way. There are several utility functions that are prime candidates for this type of re-factoring. The readability gains in the client code are quite significant. Any extension methods will need to be isolated with
> {{#ifdef NET_3_5 || MONO}}
> since this is a new feature for the .NET platform.
> See the following link for more information on extension methods:
> http://msdn.microsoft.com/en-us/library/bb383977.aspx
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.