Printing in Windows Store Apps

Question

So,
I am changing this post because my problem is far more complicated (annoying) than originally expected.  If I were creating a WinForms app I would have access to System.Drawing and the Win32 API, but as I am currently trying to create this as a Windows
Store app, it renders those possibilities moot.
The idea is to print a small 1x1 inch to a specific printer.  Now, in the Runtime intrerop functionality I could search for the printer driver and just assign that value to the PrintDocument.  Using a graphics I could just draw the in memory bitmap
to the document and send it away.
However, in this hyper security limited context of the metro interface "store app" I have found so far only Windows.Graphics.Printing and WIndows.UI.Xaml.Printing namespaces.  Though they seem to allow for sending data to
a printer thus far I have not found any indication I determine
which printer.
The whole idea is a closed box system, so no extraneous dialogs or user interactions.  They pick the image, set the quanity, and the golden hamster wheel spits out a printed label.
Now, I can do this very simply in a WinForms application, which I will be working on concurrently so I have a final product to deliver, but for myself (and the client) we would prefer a windows 8 metro style app to do this.  (now if store apps just
access the entirety of .Net that would so much simpler, but wishes and horses).
So could anyone provide me a map for more advanced control of the Printing process from a Windows Store App that I might figure out how to send the print document to the printer I want?
Thanks
Jaeden "Sifo Dyas" al'Raec Ruiner

Answer 1

Excellent, thanks for the quick reply.
For clarification, you mentioned a few terms that i would like to clarify:
1.  windows runtime component / desktop printing API
this sound like an actual windows 8 desktop application.  Like what you'd run on windows 7 and windows 8 desktop.  (Full .net 3.5/4/4.5 not the "Windows Store App").  Basically a Windows Forms application / class library / win service
maybe?
2. brokered
this term sounds like there is a way to communicate from a Windows Metro/Store (XAML) App to a windows desktop component (a process maybe?).  If so, how does one do that.  If I create a WinForms application and create a class library for it. 
That class library can be used by any .net application that references it but in the Windows Store App project I can't reference a standard class library, but your use of the term "brokered" suggests there is a way to do this.  Where would I
find how to do that?
3. desktop
Finally, by the mention of the term "desktop" red flags go up.  I personally will never use Windows RT because it lacks the desktop.  However, by the suggestions you've made here the only way to get my goal seems to be in using Windows
Desktop features.  If I were to create the XAML App and the "brokered component" to thus have access to "desktop printing", is that something that will even work on a Windows RT machine?
Thanks so much,
J"SD"a'RR
"Never Trust a computer. Your brain is smarter than any micro-chip."
PS - Don't mark answers on other people's questions. There are such things as Vacations and Holidays which may reduce timely activity, and until the person asking the question can test your answer, it is not correct just because you think it is. Marking it
correct for them often stops other people from even reading the question and possibly providing the real "correct" answer.