System.Management

  • Thread starter Thread starter eric
  • Start date Start date
E

eric

I'm writing a program in C# and found a couple of threads about how to
check the status of a printer before sending it any data, to ensure
that the printer is ready to print. They say to include the
System.Management namespace. This is where my problem is, I have no
System.Management namespace. Could anyone help me locate it or a
reference to locate it?
 
If you have .Net 2.0 then it is in
c:\windows\Microsoft.Net\v2.0\SystemManagement.dll.
 
hi i've the same problem
when i type
using System.Management;
and compile the VS gives me an error indicating that there is no namespace
named System.Management
i've tried this both on VS 2003 and VS 2005 using C# using both frameworks
1.1 and 2.0
i was trying to make a windows based application using this namespace to
fingerprint machines to protect my software from piracy
here is a link fot that code
http://www.vbforums.com/showthread.php?t=250436&page=1
the funny thing that System.Management is documented on VS 2003 but still
the VS 2003 IDE doesn't recognize it as a valid namespace
it's also documented here
http://msdn.microsoft.com/library/d...ry/en-us/cpref/html/frlrfsystemmanagement.asp
please help i really need a fast answer for this problem
thanx in advance
 
one more thing
i've reinstalled the framework and tried that on 2 machine with both VS 2003
and VS 2005 and still the problem is the same
 
really thanx alot now i can see it in the system namespace tree in VS 2003
but i would like to ask a q
y it's not standard?
 
You have to add a reference to everything that's not in mscorlib.dll or
automatically referenced when you create a new project of a certain type (eg
Windows App will reference the dll with System.Windows.Forms).

There are several dlls because it would be inefficient to load and init a
load of stuff that you aren't going to use.

As I recall the documentation now tells you the name of the defining dll for
every class etc.

One reason why there are several dlls is to allow finer control of
versioning.

(Another reason for separate dlls is for separate assemblies because
otherwise the scope of 'internal' would be too large - I'm not a fan of
internal)
 
Back
Top