Windows.Forms equired for printing?

[Phill]

It seems a reference to System.Windows.Forms is required for printing
to work. I tried printing in a console app w/o a rference to it and
got garbage. Added the reference and it works now.

Wierd, anyone seen this happen? Know why?

[Nicholas Paldino [.NET/C# MVP]]

Phill,

That's just the way that they distributed the classes, I would suppose.
The assembly has little to do with the namespace of a type. While it would
be nice that an assembly have some correlation between the namespace of the
types it contains, and the name, there is no set requirement for this.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Phill" <wa********@yahoo.com> wrote in message
news:ac**************************@posting.google.c om...

It seems a reference to System.Windows.Forms is required for printing
to work. I tried printing in a console app w/o a rference to it and
got garbage. Added the reference and it works now.

Wierd, anyone seen this happen? Know why?

[Phill]

> That's just the way that they distributed the classes, I would suppose.

The assembly has little to do with the namespace of a type. While it would
be nice that an assembly have some correlation between the namespace of the
types it contains, and the name, there is no set requirement for this.

I don't get how that correlates??

Perhaps I'm being unclear. It's not like it doesn't compile or throws
an exception. The program procedes just fine weather you reference
Windows.Forms or not. It simply does not output correctly unless you
include the reference which makes no sense since I'm not using any
classes in that dll.