[tclin]

I've been reviewed through all these issues below, I realized that its a known issue if using Visual Studio, it will not be able to call the PM web service. So, I just want to make sure that, is PM going to fix this issue (namespace problem) in the near future, either in the next version or even commercial version, in order to cater the people using .NET??

http://forum.processmaker.com/viewtopic ... vice#p6265
http://forum.processmaker.com/viewtopic ... ices#p1934
http://forum.processmaker.com/viewtopic ... wsdl#p3148
http://bugs.processmaker.com/view.php?id=3598
http://bugs.processmaker.com/view.php?id=4390
https://connect.microsoft.com/VisualStu ... and-a-type

[sogomez]

There is a solution sent to .Net Forum
http://social.msdn.microsoft.com/Forums ... ae9e57b64a

Basically, the attribute ResponseElementName="pmResponse" is duplicate in each method in the definition file generated by VIsual Studio, so must replace each value for "pmResponse2", "pmResponse3", etc.

It works to me!
One note: I followed the change in c#, but a friend tried it in VB and it doesn't work...Maybe he did something wrong.

[pmUser2000]

Basically, the attribute ResponseElementName="pmResponse" is duplicate in each method in the definition file generated by VIsual Studio, so must replace each value for "pmResponse2", "pmResponse3", etc.

for the moment we can't change the wsdl file, because there are many implementations running with this wsdl, and if we change it, probably will stop working ( if they upgrade PM )

by the way you mentioned some VB users can't run PM webservices, that feedback will help us to improve the webservices for .net users.

We have a lot of integrations done with .net. ( maybe a subset of versions have this issue ). If you have this issue the workaround of modify the PM Wsdl should be fine .