I need to make an iOS application that can consume a web service on Microsoft Dynamics NAV system. The web service is given in WSDL. I tried to access the service by sending SOAP request but without success. Is there a different approach to consume a WSDL web service on a NAV system ? I am really stuck in here. I would really appreciate some help. Thank you in advance !
My suggestion in this situation is always to create a C# Web Service that will act as a bridge between NAV and your iOS application.
The Web Service use .NET so can easily pull the data from NAV, and because is a Web Service you can consume it by any platform (with SOAP or REST is your decision)
Related
I have MVC.Net application which has it's own application insights configure and this application makes a call to WCF service(using service reference client) and the WCF service also have application insights configured.
What I'm looking for here, in WCF application insights I want to see mvc application insights component as an incoming request (Initial request) node to WCF service application insights node. Just for the information, I have installed Application Insights WCF SDK package.
Expected view application map
Firstly want to know, is this even possible and if yes, then any tips or suggestions are highly appreciated.
WCF doesn't play nicely with restoring correlation context.
Here is a github issue which tracks it for outgoing calls: https://github.com/microsoft/ApplicationInsights-dotnet/issues/1631.
You might need to do something similar (to workaround in above github issue) for incoming requests - read headers and initialize the right Activity class.
I have a standard nteir setup :-
Web server -> App server -> DB server
I have an MVC 5 web application sitting on the web server with controllers calling a WCF services project sitting on the App server. WCF services project uses EF6 to marshal data on the DB server.
I am wondering if WCF is overkill? Is there is an easier way to achieve this same architecture? I am thinking I should have gone with Web API on the app server and then just call the web API from the controllers with the HTTPClient?
Or, I could even just use a plain MVC project on the App server returning JSONResults to the MVC controller on the web server?
It depends...
You have to understand what are the benefits of each set up. This is not exhaustive, just a quick brain dump. This should give you some hints to look further as in the wild world there might be many more reasons for choosing one or another solution.
Why WCF. Are you going to have different clients to your backend ? You need some entreprisy security between clients and you backend ? With WCF you could configure Http, TCP endpoints, set message or transport security and a lot more. It could be needed for example if your doing an intranet application and you would like not only to have your UI (MVC application) but other systems going to it. If this is not needed WCF seems overkill here.
Web Api is also agreat choice if you would like to built more REST oriented api, enabling content-negotiation for different clients (different media-types). Building REST is not about issuing JSON, it's much more and this would be too long to explain it here. If your client is not only your MVC app, but you could have a need for a api for other mobile devices, OAuth authentication and the so, this could be a good way to do.
Plain MVC app would also fit if you don't have any special needs, go for it. No overhead needed. Keep It Simple And Stupid.
I hope this helps
I would not change this.
WCF is a good choice for communication between Web Tier and App Tier. I would never put my App Tier exposed to outside world, so if there is any communication to my app from outside world, it would be through Web tier only and if there is a need to support multiple clients, I would create a WebAPI on web tier and expose that.
I would keep App tier only available to Organization internal and with WCF I would have flexibility to write service code and contracts which can then be exposed over various bindings (transport, security, etc.).If you are building a service in your organization and plan to support multiple protocols, or simply use protocols other than HTTP (tcp, name pipes, udp, etc.) then WCF is indeed a good choice.
I want to use Azure service bus in my iOS app to communicate with server i have went through the below link. its pointing to C#.Need suggestions to work on iOS.
http://azure.microsoft.com/en-us/documentation/articles/service-bus-dotnet-how-to-use-relay/#next_steps
You may want to consider using WebHttpRelayBinding for your service so you can hit the Azure endpoint using HTTP / HTTPS.
WCF supports both RESTfull and classic SOAP style messaging but using lightweight json requests in a RESTfull service would be better from a mobile app.
read the following article for details. but you don't need to write custom autostarter if you are using IIS 7.5 or greater with appfabric, since it has autostart functionality in built.
http://msdn.microsoft.com/en-us/library/hh966775.aspx
if you don't need request-response messaging pattern then you can also consider service bus queues for persistence, and your on-premise process can pull and process the messages at its own pace.
Can i have mechinism to have push notification to .NET MVC application once user comes online? Like facebook and gmail? I am going to deploy my app in 3 part.
1) MVC application
2) WCF Service
3) Azure SQL
Everything would in Windows Azure.
Thanks.
If I understand your question correctly, then you might be interested in SignalR. Here is the link http://signalr.net. SignalR allows you to push content from the server to the client. It comes with client side js library and also server side component. SignalR is very easy to implement and provides a very powerful set of abstractions that otherwise would be very difficult to program.
I have a MVC web application and I make some ajax calls from the client to get back json data. Right now I just use MVC Action methods to return this data. I was wondering if I should be using the ASP.Net Web Api for these.
I understand that if I was building a REST solution I should be using it.
But in this case would it be justified to add the extra complexity? Is there any speed gain? I don't really need the Content Negotiation feature or the OData Support.
According to the post here (and the benchmark it references), Web API is a bit faster. Web api performance?
ASP.net Web api support both JSON and xml. Web Api is for implement rest web service on top of MVC application. It would add extra complexity for the application but you implement web api related method in separate controller.
Rest web services are usually faster than Normal SOAP web services.
In your case if your clients are just a web client no need to implement web services. But If you need to share service for different client (widows applications, windows services, third party applications) implement rest service using web API