Is there a reason why to not use a service reference? Web reference is deprecated, still every example I have seen uses it for Navision, even the newest MSDN guide for Nav 2016 linked below.
*This post is locked for comments
Maybe I should have read more carefully. The article actually brings this up:
"Visual Studio 2005, Visual Studio 2008, Visual C# 2008 Express Edition, or any version of Visual Studio that supports adding Web references. You can also use service references instead of Web references or the Web service proxy generating tools (svcutil.exe or wsdl.exe) that are supplied in the Microsoft .NET Framework SDK."
So using a service reference is perfectly fine which makes sense as how you consume a web service should not matter.
We have been using service reference without any problems so far, what is it that is not supported?
the service reference is meant for WCF services, not for web services. for web services (SOAP) like the nav web services it's needed to use the "old" web reference. the for wcf services needed additional settings are not supported by nav web services.
Share
Report
All responses (
Answers (
32,727
