| Author |
Message
|
| cr |
 Posted: Fri Oct 20, 2006 4:32 am Post subject: MQQueue MQManager MQMessage not CLS-compliant(.NET question) |
 |
|
Novice
Joined: 04 Oct 2006
Posts: 12
|
Hi again
I'm referencing the types MQQueue MQManager MQMessage in amqmdnet.dll in an assembly that is marked as CLSCompliant. Ultimately these type won't be exposed in the public 'interface' of the assembly but I'm wondering if anyone knows what is about them that makes them not CLS compliant?
The error message doesn't give any clues:
warning CS3001: Argument type 'IBM.WMQ.MQQueue' is not CLS-compliant
From what I've read in MSDN I can't quite see what it is about these type that are causing the warning.
Anyone been through this?
Thanks for any comments.
cr |
|
| Back to top |
|
 |
| cr |
| Posted: Fri Oct 20, 2006 4:40 am Post subject: |
|
|
Novice
Joined: 04 Oct 2006
Posts: 12
|
Update :-)
I know uint is not CLS compliant so here's my guess.
MQMessage has a public method To370fp(byte*, uint, double).
MQQueue uses MQMessage in its public interface.
MQQueueManager uses MQQueue in its public interface.
So, because of that pesky To370fp, I'm getting the warning on all three!
Anyone agree that this is the only reason?
Cheers
cr |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Oct 20, 2006 5:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You might look at FP2 of v6, and the Managed Client. It might not have these same issues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| cr |
| Posted: Mon Oct 23, 2006 12:33 pm Post subject: |
|
|
Novice
Joined: 04 Oct 2006
Posts: 12
|
Hi
Just on version 5.3. Are you saying they've changed the API in a newer version to make it compliant? Wouldn't that break the old ones?
Cheers
cr |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 23, 2006 4:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm saying that the Managed Client is not going to be built on top of the C client library. Ergo, it is likely going to use "native" .NET data types, rather than having to use particular datatypes to match up with the C library data types.
I've never heard of that To370fp method call. If it's a public method, it's still probably not intended for public use. So it's also possible that this method has been made properly private in a later FP of the .NET interface.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
