I wanted to know if an Odata service can be hosted as a windows service?
It is definitely possible. The question is what server technology you want to use. If you want to use WCF Data Services, then it supports custom hosting. See this description to start with: http://msdn.microsoft.com/en-us/library/cc668805.aspx
Related
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)
I have plain old SOAP "REST" service written in WCF which is hosted on Azure as WebRole. I am currently writing website which will consume this service and show some nice GUI for it. WebSite will be hosted as WebRole too and is written in ASP MVC 5.
Now i am looking for some Synchronization Framework i can implement into both sides (website and service). There will be more clients than web-site (Store app, Desktop client, android etc.)
Now i came to SignalR and XSockets.net but. Can these frameworks be scaled to more instances automaticaly and how that exactly work? For signalR i found it uses ServiceBus as background does Xsockets have simmilar? For Xsockets i found some issue page which look kinda new, but there is not a word about scalability.
By default XSockets scale over sockets and not SQL or redis. If you want to scale over something else just write your own plugin.
https://github.com/XSockets/XSockets.NET-4.0
Is it possible to consume WebAPi into windows service. Because WebAPI is http protocol, so iam not sure weather i will consume WebApi.
I tried search for consuming WebAPI with Windows service. I can't even find single examples.
Can any face similar kind of scenario
Yes we can able able to consume WebAPi inside the Windows service. Since it is windows based service we need consume it with HttpClient object.
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.
I have a web service app - that I need to connect to a MOSS server.
for example:
using (SPSite site = new SPSite(this.SiteAddress ))
{
using (SPWeb web = site.OpenWeb())
MOSS is not running on the same server as this web service app. Should this be a problem trying to use the object model. Or do I really have to go the web service route?
As far as I know you need SharePoint installed to use the object model (you may be able to fudge it, but I wouldn't fancy your chances :-)). You options are to either use the built in SharePoint webservices, expose your own "friendly" service and consume it from your other server or move your webservice to the Sharepoint box.
At the very minimum you will need to deploy Microsoft.SharePoint.dll to the machine hosting the web service. If it does require MOSS classes (the one's you've listed only require WSS) then you will also need to deploy the MOSS assembly (I believe it's Microsoft.Office.Server.dll). After that, it's going to become a deploy and pray situation in my experience :)