I've designed a solution that I don't know how to implement entirely.
I have created a scheduled report generator. I need it to run 24/7 so it can output reports on a schedule. I'm using an NT Service to start this function.
My desire is to also have the processing information accessible from an ASP.NET web page. I'd like to start/stop it, but that appears to setup a IIS hosted process. At least get status information would be good.
I've started down the road of having the print function in a WCF service with a BackgroundWorker running, thinking that I can get to the same WCF instance from the web form, and get status information. I am at the point where
the service will run, but I am unable to connect from an ASP.NET page (or from a forms app).
I guess my question is, if the WCF service is hosted in ServiceHost via netTcpBinding, should I be able to connect to it from an outside UI and get the instance that was started by the ServiceHost? Perhaps using basicHttpBinding?
Suggestions or recommendations are appreciated. Web links and reading are great.
Thanks in advance.
View Complete Post