I currently have a windows form application which is used for printing receipts. How it works->
- Browser uses custom url protocol to trigger the windows form app and and also passes a payload to the app.
- Windows app passes this payload at a url endpoint and retrives printing data.
- After receiving data, we use
System.Drawingand it's related functionalities to print the data.
Problem in this approach->
- This kind of printing requires active internet connection (for url request).
- Size of payload that can be passed through custom url protocol is limited.
What i am trying to do: I am building a client facing printing solution which does not require active internet connection (for api request). To pass printing data, i am trying to use socket based approach to pass data from browser to a windows app or service.
How this new app is supposed to work: Is has to be always active and ready to receive data from browser on a socket connection (like a service) and print it.
What i tried: I have made a windows service that listens to a particular port and receives data by i am not able to print using it. I found this which suggests it's really cumbersome.
Now i am looking to implement similar functionality in my existing app but i am stuck. Any help would be highly appreciated
