- 0
Printing across a network using C#
-
Recently Browsing 0 members
- No registered users viewing this page.
-
Posts
-
-
By eilegz · Posted
it was a mobile OS first thats why its UI its so bad, the same with windows 8 which was more designed for tablets and again not as a desktop OS first. -
By eilegz · Posted
"vista rebranded" lol w7 works, its not slow and sluggish we cant say the same thing about vista that run like crap even on new machines. -
By eilegz · Posted
just get iot enterprise ltsc 2021 thats the w10 with support until 2032 -
Rufus 4.9.2256 by Razvan Serea Rufus is a small utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc. Despite its small size, Rufus provides everything you need! Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO (with honorable mention to WiNToBootic for managing to keep up). It is also marginally faster on the creation of Linux bootable USBs from ISOs. A non-exhaustive list of Rufus supported ISOs is available here. It can be especially useful for cases where: you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.) you need to work on a system that doesn't have an OS installed you need to flash a BIOS or other firmware from DOS you want to run a low-level utility Rufus 4.8.2253 changelog: Switch to wimlib for all WIM image processing: Greatly speeds up image analysis when opening Windows ISOs Can speed up Windows To Go drive creation (But won't do miracles if you have a crap drive) Might help with Parallels limitations on Mac (But Rufus on Parallels is still unsupported) Enables the splitting of >4GB files with Alt-E (But still WAY SLOWER than using UEFI:NTFS) Others Switch to using Visual Studio binaries everywhere, due to MinGW DLL delay-loading limitations Add more exceptions for Linux ISOs that restrict themselves to DD mode (Nobara, openSUSE, ...) Improve reporting of UEFI bootloaders in the log, with info on the Secure Boot status Fix an issue with size limitations when writing an uncompressed VHD back to the same drive Fix a crash when opening the log with the 32-bit MinGW compiled version Fix commandline parameters not being forwarded to original Windows setup.exe Rufus 4.9.2256 fixes: Fix downloads from https://rufus.ie no longer working due to recent GitHub server changes Fix unofficial Windows ISOs, with single index WIMs, not presenting the WUE dialog Download: Rufus 4.9 | Portable | ~2.0 MB (Open Source) Download: Rufus 32-bit | ARM64 Links: Rufus Home Page | Project Page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
-
-
Recent Achievements
-
Legend20 went up a rank
Explorer
-
jezzzy earned a badge
One Month Later
-
CSpera earned a badge
First Post
-
MIR JOHNNY BLAZE earned a badge
One Month Later
-
Wireless wookie went up a rank
Apprentice
-
-
Popular Contributors
-
Tell a friend
Question
ramesees
Hi all
I am currently writing a service that will run once per day, retrieve data from a SQL database, and print some reports.
Here is the problem:
I have an xml config file which contains a report code (eg RPT001) and the printer it is to print to. This means that in future if I want to, I can simply change the printer name without too much disruption and the reports will be redirected elsewhere.
However, I am unable to set the printer name so that the report gets printed out. When I use :
// If we have specified a printer name print to this one otherwise the
// default printer will be used
if (_printerName != "")
{
pd.PrinterSettings.PrinterName = String.Format("{0}", _printerName);
}
A call to pd.PrinterSettings.IsValid, always returns false.
I have been looking into the PrintingPermissions topic, however I am unable to find a proper clear sample of how to use it so that I can grant access to my code to be able to print across the network.
The printers are connected to a central print server, however specifying "\\servername\printer" doesnt seem to work either.
To complete the picture, the code which performs the printing is in its own DLL and the service references this DLL.
What changes need to be made and where to get this to work?
Any and all help is very much appreciated :D
Link to comment
https://www.neowin.net/forum/topic/613622-printing-across-a-network-using-c/Share on other sites
16 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now