I've written a C#.NET (3.5 Framework) Application for a business - the Application prints invoices.
I developed and tested the Application on Windows XP at my home using a shared network printer to test the print functionality of the Application and it functioned perfectly.
Due to incompatibilities between a few devices, the target platform of the Application was then changed to Windows 8.
When run on Windows 8 (on site at the businesses premises) using a wireless printer (a Kodak ESP 1.2), no errors are thrown by the Application when attempting to print documents. All invoices are added to and removed from the print job list (in a matter of seconds) but the invoices are not being printed by the printer. All other applications installed on this machine were able to print documents immediately.
To narrow down the problem I tested the same Application on a Windows Vista machine (again, on site at the business, using the same wireless printer as that installed on the Windows 8 machine) and the application functioned perfectly.
I then tested the Application on Windows 7 (at home) using a shared network printer (the same one denoted in the second paragraph). After print was selected on the Windows 7 machine, it took a full seven minutes for the printer to start printing on the first occasion; however all invoices printed after this were printed immediately. As was the case with the Windows 8 machine, all other applications installed on this machine were able to print documents immediately.
Where the Windows 7 machine eventually printed invoices after a long delay, the Windows 8 machine failed to print invoices at all (I worked on this problem on site at the businesses premises this week for a full 8 hours and no invoices were printed during my time there).
It may also be worth noting that the printer used to test both the Windows 7 and Windows 8 machines were only installed a few minutes before testing was begun.
Is it possible that it may take the Application may take some time to connect to the printers on the initial execution?
Is it possible that this could be caused by a Firewall setting (this was my initial presumption)?
Any help is much appreciated as this driving me insane!