| Author |
Cannot use common objects on both client and server side
|
|
| zorrinn 2005-09-15, 3:53 pm |
| I added a reference (.NET library) to my BizTalk project, say "Common" and I have used one of the .NET classes(objects) to be an incoming message type, say "Common.MyClass".
I have now published an orchestration as a webservice.
Thus the webmethod would be method1(Common.MyClass obj)
I then added the webservice as a web reference ("webref") to my client application. One of the other references is the same "Common".
When I try to pass the object of type Common.MyClass to my webmethod, I get a compiler error saying that the method signature is method1(webref.Common.MyClass obj)
What do I do??? | |
| zorrinn 2005-09-16, 4:04 pm |
| quite simple. but tricky.
When you add a web reference to your client application, the generated file Reference.cs which is a client side proxy of your server object (web service), the namespace is added the same as your local namespace of that client project.
To avoid this, create the client side proxy class using the wsdl.exe tool and add it to your client project. This way it does not create a namespace in the generated class. | |
| zorrinn 2005-09-16, 4:33 pm |
| How do you create a message type of type long integer. The only ones I see in the properties are System.String and System.DateTime, apart from other referenced standard .NET class in which I cannot find System.Long
Is it ever possible to create a message type of type System.Long?
Also, can I send back an array of .NET objects[] ?? | |
| zorrinn 2005-09-19, 8:59 am |
| I guess my questions are so dumb that no one replies. I reply to my own postings after I spend a long time figuring out things myself.
Anyway, I still haven't found a way to send back a long integer from an orchestration. I am also wondering how to send back a boolean.
Let me know. Thanks. |
|
|
|