How To: Retrieve a Printer Device Context.I imagine that you will also find the following two how-to articles useful: Once you've created a Graphics object that represents your device context, and created an Image object from your image, you'll call the DrawImage instance method of your Graphics object to do the actual drawing. Using GDI+, there will be two primary classes that you'll use: the Graphics class (which encapsulates a device context), and the Image class (which represents images, including PNGs). It works as far back as (at least) Windows 2000, although on those older versions it does require a redistributable DLL. It has a nice C++ API, but it's also usable from C. To save you a lot of reading, though, the simple answer is that you need to use GDI+ instead of GDI. That topic was covered in more detail by this question and plenty of others here and elsewhere on the web. Working with a PNG as opposed to, say, a bitmap (BMP) is made somewhat more difficult by the fact that GDI does not natively support PNGs. This can be either text or graphics-a PNG image in your case. Once you have the printer device context, you just need to draw whatever you want into it. The documentation I linked to earlier should get you started, but in case you can't find it, the link you want is this one. So your first order of business is to create/obtain a printer device context. Printer device contexts work much the same way. You've already used screen device contexts if you've drawn anything to the screen. There are device contexts for the screen (i.e., the monitor), and there are also device contexts for the printer. This is how Windows abstracts away the myriad differences between different types/brands of output devices and allows the programmer to write the same code for all of them. If you're at all familiar with Windows programming already *, you surely know that all graphics operations involve drawing onto or otherwise manipulating device contexts. Since the question shows little to no research effort, I'm going to treat it like a homework question and provide pointers in the right direction as opposed to a complete solution…

Printing from ms visual studio code