All geek questions in one place

Silverlight 4, from a browser, print, automatic updates

I have a very critical business application currently working with Winforms.

The application is the very core of the user interface shell. It takes input, calls a web service on my server to perform the calculations, displays the results in the winforms application, and finally sends the print stream to the printer.

The application is currently being deployed using Click-once.

Moving forward, I am trying to consider how I should move an application to a Silverlight application. A couple of reasons why I think silver.

  • It gives customers the feeling that it is a cloud solution.
  • Access to any PC. Although the clickonce application can also do this, it needs to install the application, and when updates are available, you need to click “Yes” to update.
  • Currently, the application has a drop-down list of customers, this list has expanded to more than 3,000 entries. Scrolling through the list is very painful. With Silverlight, I think of automatic ability.
  • From the browser - it will be convenient for those users who use the application daily.

I have not used Silverlight before, so I looked for some expert advice on a few things:

  • Print - Allows Silverlight to send raw print data to the printer. The application prints on a Zebra Thermal printer. I have to send the raw bytes to the printer using commands. Can this be done using SL or will it always ask for the Print dialog?
  • In the browser - when SL applications are installed both from the browser, how does the update happen, is the application updated automatically, or is the user prompted to select the update?
+4
source share
2 answers

  • Print. Using the PrintDocument API, your user will be prompted to open the print dialog. Using this API does not resolve this at this time. It is not ideal for intense thermal situations (such as pharmacies, warehouses, etc.). You can use the trusted application mode and look into COM and do whatever you want with a printer.

  • An update occurs when the application requests it. There is an API to use and, after a call, if an update exists, it loads - there is no invitation to the user as an option. If an update is found, you can warn the user about a restart or that the next time they restart, they will have an updated application.

+4
source

Autocomplete is not something that can only be done in Silverlight. ClickOnce is already out of the browser. And printing through raw bytes to the thermal printer is something that is not easily designed in Silverlight.

Don't try to sound negative, but overall it sounds like you're better off just working on improving the application that you already have.

+1
source

Source: https://habr.com/ru/post/1312032/

More articles:


All Articles