Find all our projects in development below.
All source code is GNU General Public License (GPL)
Browsing frmProcessProps.resx (8.71 KB)
<?xml version="1.0" encoding="utf-8"?>
<root>
<!--
Microsoft ResX Schema
Version 2.0
The primary goals of this format is to allow a simple XML format
that is mostly human readable. The generation and parsing of the
various data types are done through the TypeConverter classes
associated with the data types.
Example:
... ado.net/XML headers & schema ...
<resheader name="resmimetype">text/microsoft-resx</resheader>
<resheader name="version">2.0</resheader>
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
<value>[base64 mime encoded serialized .NET Framework object]</value>
</data>
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
<comment>This is a comment</comment>
</data>
There are any number of "resheader" rows that contain simple
name/value pairs.
Each data row contains a name, and value. The row also contains a
type or mimetype. Type corresponds to a .NET class that support
text/value conversion through the TypeConverter architecture.
Classes that don't support this are serialized and stored with the
mimetype set.
The mimetype is used for serialized objects, and tells the
ResXResourceReader how to depersist the object. This is currently not
extensible. For a given mimetype the value must be set accordingly:
Note - application/x-microsoft.net.object.binary.base64 is the format
that the ResXResourceWriter will generate, however the reader can
read any of the formats listed below.
mimetype: application/x-microsoft.net.object.binary.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.soap.base64
value : The object must be serialized with
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
: and then encoded with base64 encoding.
mimetype: application/x-microsoft.net.object.bytearray.base64
value : The object must be serialized into a byte array
: using a System.ComponentModel.TypeConverter
: and then encoded with base64 encoding.
-->
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
<xsd:element name="root" msdata:IsDataSet="true">
<xsd:complexType>
<xsd:choice maxOccurs="unbounded">
<xsd:element name="metadata">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="name" use="required" type="xsd:string" />
<xsd:attribute name="type" type="xsd:string" />
<xsd:attribute name="mimetype" type="xsd:string" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="assembly">
<xsd:complexType>
<xsd:attribute name="alias" type="xsd:string" />
<xsd:attribute name="name" type="xsd:string" />
</xsd:complexType>
</xsd:element>
<xsd:element name="data">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
<xsd:attribute ref="xml:space" />
</xsd:complexType>
</xsd:element>
<xsd:element name="resheader">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string" use="required" />
</xsd:complexType>
</xsd:element>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:schema>
<resheader name="resmimetype">
<value>text/microsoft-resx</value>
</resheader>
<resheader name="version">
<value>2.0</value>
</resheader>
<resheader name="reader">
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<resheader name="writer">
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
</resheader>
<metadata name="tooltipHelp.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
<value>17, 17</value>
</metadata>
<data name="lblPrivilegedTime1.ToolTip" xml:space="preserve">
<value>The total elapsed time this process has been running in Privileged Mode
in non-idle threads. The service layer, the Executive routines, and the
Kernel execute in Privileged Mode. Device drivers for most devices other
than graphics adapters and printers also execute in Privileged Mode.
Some work that Windows does for your application may appear in
other subsystem processes in addition to Privileged Time.</value>
</data>
<data name="lblUserTime1.ToolTip" xml:space="preserve">
<value>The cumulative elapsed time that this process’s threads have
spent executing code in User Mode in non-idle threads.
Applications execute in User Mode, as do subsystems such as
the window manager and the graphics engine. </value>
</data>
<data name="lblProcessId.ToolTip" xml:space="preserve">
<value>The unique ID of this process. Process ID numbers are reused,
so they identify a process only for the lifetime of that process.
The Process object type is created when a program is run.
All the threads in a process share the same address space and
have access to the same data.</value>
</data>
<data name="lblNonpagedPoolSize1.ToolTip" xml:space="preserve">
<value>The current number of bytes in the nonpaged pool allocated by the process.
The nonpaged pool is a system memory area where space is acquired by
operating system components as they accomplish their appointed tasks.
Nonpaged pool pages cannot be paged out to the paging file; they remain
in main memory as long as they are allocated.</value>
</data>
<data name="lblPagedPoolSize1.ToolTip" xml:space="preserve">
<value>The current amount of paged pool the process has allocated. Paged pool is a
system memory area where operating system components acquire space as
they accomplish their appointed tasks. Paged pool pages can be paged out
to the paging file when not accessed by the system for sustained periods of time.</value>
</data>
<data name="lblWorkingSet1.ToolTip" xml:space="preserve">
<value>The set of memory pages touched recently by the threads in the process.
If free memory in the computer is above a threshold, pages are left in the
Working Set of a process even if they are not in use. When free memory
falls below a threshold, pages are trimmed from the Working Set.
If theyare needed, they will be soft-faulted back into the Working Set
before they leave main memory.</value>
</data>
<data name="lblVirtualSize1.ToolTip" xml:space="preserve">
<value>The current size (in bytes) of the virtual address space the process is using.
The use of virtual address space does not necessarily imply corresponding
use of either disk or main memory pages. However, virtual space is finite,
and using too much may limit the ability of the process to load libraries.</value>
</data>
</root>