I'm currently making an desktop application for the company I work for. The goal of the application is to control the flow of a manufacturing process and it will be used by 5-7 user (working of remote desktop clients) with different UI windows, two to input orders into a database and the remaining (like in a manufacturing assembly-line) change the status of those orders until complete.
I started building the application in C# Windows forms with a SQLite db for data storage and rendering the views with CEFSharp (Chromium).
My original idea was to somehow deploy the application in the network, perhaps just using the DLLs and .exe and monitor the database for changes to update the views. I've since seen that SQLite not having a server will make listening to the db difficult.
I thought about trying to create a timer tick in the client to check for changes or perhaps have a service that starts as soon as one client is using and passes messages between themselves (signalr or a socket) but I don't know the implication of that on the network.
I'm locked into a corner due to the restrictions imposed by the business and I'm afraid I'm creating a broken application from the start.
The restrictions are: No installation required for the application, information flow needs to be "live", they would prefer not to have a local server running, and it needs to work offline, besides their system/network administration team being anything but helpful.
My question is, is it at all possible to build & deploy this application with this requirements and without disrupting their network (in this or another tech stack)? And which would the better approx to be?