I have process which continuously downloads XML from the feed and saves it to DB.
I have a Windows Shared Hosting.
My question is what should I use..WCF or Windows Service or Web Service.
I cant use ASP.net because it will run on call only...but I need it run 24/7.
Can you guyz suggest me how to design it?
I have written a Windows Service but was unable to run it on the Server.
My hosting provider is Hostgator.com
You need to do it in a Windows Service.
To run it you'll need a VPS hosting (or dedicated, but it will cost much more).
Start with building a Console Application that does what you need. After you have it look online how to convert it to a windows service.
Related
I am working in windows application which consumes WCF services(http) which are hosted in another server.Initial load of this application is too high.
To find out root cause of the issue, I would like to see the network traffic when the windows application is running in my machine and i want to know how much time it is taking to make calls and get data from service.
Is there any tool to capture the network traffic when the windows application is running on the desktop.
thanks
For WCF, you will want to use use WCF tracing. Here is an SO article that talks about how to enable it: How to turn on WCF tracing?
I'm working on a project that consists of a web application where users can start long process of generating different types of files.
User wont be able to download the files, only can start the process and the files will be located on the server and this process could take several hours.
My Idea to solve this its a MVC App that is communicate with a windows service and this service start the file generation process.
I have some concerns about this.
based on your experience, do you think that is the best way to solve the problem?
What is the best and easiest way to communicate the web app and the windows service? this is a one way communication, web to service.
About the windows services; should the service do all the processes? or maybe its better if the service only execute console applications that do the generation o the different type of files.
I really appreciate your help.
Since Web API can be self-hosted in any process and a Windows service isn't an exception, I would recommend hosting both HTTP API and the long process thing in the same Windows service.
Use OWIN/Katana to host your Web API.
Use Topshelf to create your Windows service.
If you design and implement this Windows service using best practices, it should be a good solution, and you should think about how easy will be the deployment of your solution since you don't need IIS anymore.
I would go still with the IIS. This is because of its support. Have been using Web webservice to host long running background service for long time without issues. Only concern is to remove the default application recycling.
Of course your application will need to handle properly start/stop events.
In advance, sorry for stupid question, but all search results in google are off-topic for me.
I want to create a C# application, that will run continuously on an Azure VM. It should NOT be event driven, as it will use different factors (db monitoring, time schedule, overall usage) to decide its activity.
Now, should I just create a console app in VS Express 2013 for Desktop and run it using RDP on VM? Or is there some azure-specific project that I can use (maybe for better integration with management portal)? All I can see and find is web-related (a website, a webjob, a background worker, a webapi), and mine app will not in any way be accessed remotely (it will periodically check db shared with a ASP.NET website)
It is possible. You should create the equivalent of a Windows Service, but then for Azure.
There is a useful question for that already on SO: Windows Service to Azure?
It has a reference to a full walk though: Migrating a Windows service to Windows Azure.
The corresponding azure type is "Cloud Services / Worker role". They work just as windows services.
So you can basically take all classes from your windows service (except Service1.cs) and put them in the new azure project.
The copy all start/stop code from your Service1.cs to the corresponding class in your new Cloud service project.
http://www.windowsazure.com/en-us/documentation/articles/cloud-services-dotnet-multi-tier-app-storage-4-worker-role-a/
Im looking at creating a service on a remote server that a win forms app can communicate with. (Where the forms app is running locally on user machines).
The service can either run in IIS (7.5) or as a windows service, but essentially I need to be able to call the service from the forms app and then have a stream of progress sent back to the forms app from the service, much like you would output to a Console window.
I've looked into using WCF which seems ideal except I couldn't find out whether I can relay progress updates back to the forms app. Also SignalR running as a self hosted windows service seems to be an option but might be overkill?
We'll be running the forms app on win7 and the remote server will be running server 2008.
Are you able to advise best routes to go down for this and if possible some examples or tutorial links?
Many thanks :-)
If you are looking for the application to relay back to the server for progress, seems you are looking for something like this:
WCF Duplex
It basicly enable you to call bi-directional function using open socket.
Hope it helps.
Thanks,
Amir
I have another annoying Metro/WCF problem :((
I have an app that uses COM object for connecting with some server.
I've created WCF Service Library which connects with server and my Metro application in one solution.
When I run it from Visual Studio debug it goes all ok.
But now I need to deploy my app onto my tablet PC for testing purposes.
I successfully deployed my test-certified Metro-application on the destination PC, but I can't understand, how can I deploy my WCF Service on it and start to listen for connections :(
I heard that I can achieve this by hosting my service in IIS, but I'm extremely new to IIS and I don't understand what-buttons-to-click :((( I don't know what's an ASP and kind of this..
And I want to know - how can my app customers will run my application without needing to deploy IIS and so on.... when my app goes in Windows Store.
Please, if anybody knows how to achieve my goals - help me if you can.
Thank you everybody!!!
Have a nice day :)