A beauty of Web services is that they don’t need to care at all about who’s consuming them. Whether there is .NET on Windows, Java on Linux or some proprietary stuff on an iPad on the other end, they do exactly the same stuff.
Once upon a time, Freddy has delivered a great series on connecting to NAV Web Services from a smorgasbord of technology flavors. If you are a .NET enthusiast, like me, the obvious choice is to connect through the tools that are at your disposal in Visual Studio: the proxy classes.
You use Visual Studio to debug objects that run in the RoleTailored client. This procedure describes how to attach Visual Studio to the Microsoft Dynamics NAV Server service before you start debugging. Before you start this procedure, you must do the following:
This example shows how to get list of windows services installed on local computer.
This example shows step-by-step how to create a windows service in Visual Studio.
The most common problem I am hearing from my friends now a days is ‘Microsoft Dynamics Service is connecting to different DataBase than Customconfig file database..’.
Recently I run into a problem where NAV service did shut down every time I did add or delete a user.
Vertalen
