[
https://issues.apache.org/activemq/browse/AMQNET-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan moved AMQ-395 to AMQNET-39:
------------------------------------------
Fix Version/s: (was: 4.0 RC2)
1.0
Affects Version/s: (was: 3.2)
Key: AMQNET-39 (was: AMQ-395)
Project: ActiveMQ .Net (was: ActiveMQ)
> The dotnet project ActiveMQ does not build
> ------------------------------------------
>
> Key: AMQNET-39
> URL: https://issues.apache.org/activemq/browse/AMQNET-39
> Project: ActiveMQ .Net
> Issue Type: Bug
> Environment: Windows XP, compiling with Visual Studio 2003, .NET
> Framework 1.1
> Reporter: Mathieu DESPRIEE
> Fix For: 1.0
>
>
> The dotnet library embedded in the last release (3.2) does not compile on
> Visual Studio .NET.
> This is due to :
> - a lot of typos ( startWith instead of StartWith, indexOf instead of
> IndexOf, ...)
> - mismatch on methods and type analysis ( if (destination is Topic) instead
> of if (destination.IsTopic()) )
> - Temporay* classes (ActiveMQTemporaryQueue, ActiveMQTemporaryTopic) do not
> exist
> - some TODO remains ( // TODO Serialization, generates a "not all code paths
> return a value" error)
> - constant values not declared (or referenced) in the good class
> (ACTIVEMQ_MESSAGE)
> - some impossible casts or conversions
> - etc.
> This is bad news, because I think a .NET component that can manipulate JMS
> messages REALLY lacks in our world of interoperability.
> I'm trying to find such a library since days, and I can't find anything that
> suits my needs. This library would be a VERY good candidate.
> Mathieu D.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
