ChannelFactory create exception
-
Hello everybody, I don't know if I omits something or if I've not correctly understanded something, but I've an Strange exception. This is the code who generates the exception :
NetTcpBinding^ binding = gcnew NetTcpBinding(); binding->Name = "IMyWebService"; EndpointAddress^ address = gcnew EndpointAddress("myUrl"); ^> factory = gcnew ChannelFactory(binding, address);
Exception System.ArgumentNullException occurs on last line. "All parameter names used in operations that constitute a service contract must be not null. Parameter name : name" Have you any idea why I'm receiving this exception ? Many thanks for your help Best regards,Syncerely yours,
-
Hello everybody, I don't know if I omits something or if I've not correctly understanded something, but I've an Strange exception. This is the code who generates the exception :
NetTcpBinding^ binding = gcnew NetTcpBinding(); binding->Name = "IMyWebService"; EndpointAddress^ address = gcnew EndpointAddress("myUrl"); ^> factory = gcnew ChannelFactory(binding, address);
Exception System.ArgumentNullException occurs on last line. "All parameter names used in operations that constitute a service contract must be not null. Parameter name : name" Have you any idea why I'm receiving this exception ? Many thanks for your help Best regards,Syncerely yours,
-
You need to use the debugger to examine both of the new objects and see exactly which property is causing the exception.
Hi, Thanks for your reply. Of course. Objects have been examined but no null name parameter was found. I've tested using configuration file on the Web service to define the service, behavior, ... rather than using code only. But same error. Debugger was checked on both side (client / service). Very strange. Regards,
Syncerely yours,
-
Hi, Thanks for your reply. Of course. Objects have been examined but no null name parameter was found. I've tested using configuration file on the Web service to define the service, behavior, ... rather than using code only. But same error. Debugger was checked on both side (client / service). Very strange. Regards,
Syncerely yours,