mirror of https://github.com/icsharpcode/ILSpy.git
9 changed files with 366 additions and 70 deletions
@ -0,0 +1,94 @@
@@ -0,0 +1,94 @@
|
||||
<?xml version="1.0" encoding="utf-8"?> |
||||
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema"> |
||||
|
||||
<!-- This is the file that defines the actual layout and type of the commands. |
||||
It is divided in different sections (e.g. command definition, command |
||||
placement, ...), with each defining a specific set of properties. |
||||
See the comment before each section for more details about how to |
||||
use it. --> |
||||
|
||||
<!-- The VSCT compiler (the tool that translates this file into the binary |
||||
format that VisualStudio will consume) has the ability to run a preprocessor |
||||
on the vsct file; this preprocessor is (usually) the C++ preprocessor, so |
||||
it is possible to define includes and macros with the same syntax used |
||||
in C++ files. Using this ability of the compiler here, we include some files |
||||
defining some of the constants that we will use inside the file. --> |
||||
|
||||
<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. --> |
||||
<Extern href="stdidcmd.h"/> |
||||
|
||||
<!--This header contains the command ids for the menus provided by the shell. --> |
||||
<Extern href="vsshlids.h"/> |
||||
|
||||
|
||||
<Include href="ILSpyAddIn.vsct" /> |
||||
|
||||
<!--The Commands section is where we the commands, menus and menu groups are defined. |
||||
This section uses a Guid to identify the package that provides the command defined inside it. --> |
||||
<Commands package="guidILSpyAddInPkg"> |
||||
<!-- Inside this section we have different sub-sections: one for the menus, another |
||||
for the menu groups, one for the buttons (the actual commands), one for the combos |
||||
and the last one for the bitmaps used. Each element is identified by a command id that |
||||
is a unique pair of guid and numeric identifier; the guid part of the identifier is usually |
||||
called "command set" and is used to group different command inside a logically related |
||||
group; your package should define its own command set in order to avoid collisions |
||||
with command ids defined by other packages. --> |
||||
|
||||
|
||||
<!--Buttons section. --> |
||||
<!--This section defines the elements the user can interact with, like a menu command or a button |
||||
or combo box in a toolbar. --> |
||||
<Buttons> |
||||
<!--To define a menu group you have to specify its ID, the parent menu and its display priority. |
||||
The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use |
||||
the CommandFlag node. |
||||
You can add more than one CommandFlag node e.g.: |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
If you do not want an image next to your command, remove the Icon node /> --> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenReferenceInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyRefGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>Open in ILSpy</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenProjectOutputInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyProjGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>Open output in ILSpy</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenCodeItemInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyCodeItemGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>Open code in ILSpy</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<Strings> |
||||
<ButtonText>ILSpy</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
</Buttons> |
||||
|
||||
|
||||
</Commands> |
||||
|
||||
|
||||
</CommandTable> |
@ -0,0 +1,92 @@
@@ -0,0 +1,92 @@
|
||||
<?xml version="1.0" encoding="utf-8"?> |
||||
<CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema"> |
||||
|
||||
<!-- This is the file that defines the actual layout and type of the commands. |
||||
It is divided in different sections (e.g. command definition, command |
||||
placement, ...), with each defining a specific set of properties. |
||||
See the comment before each section for more details about how to |
||||
use it. --> |
||||
|
||||
<!-- The VSCT compiler (the tool that translates this file into the binary |
||||
format that VisualStudio will consume) has the ability to run a preprocessor |
||||
on the vsct file; this preprocessor is (usually) the C++ preprocessor, so |
||||
it is possible to define includes and macros with the same syntax used |
||||
in C++ files. Using this ability of the compiler here, we include some files |
||||
defining some of the constants that we will use inside the file. --> |
||||
|
||||
<!--This is the file that defines the IDs for all the commands exposed by VisualStudio. --> |
||||
<Extern href="stdidcmd.h"/> |
||||
|
||||
<!--This header contains the command ids for the menus provided by the shell. --> |
||||
<Extern href="vsshlids.h"/> |
||||
|
||||
<Include href="ILSpyAddIn.vsct" /> |
||||
|
||||
|
||||
<!--The Commands section is where we the commands, menus and menu groups are defined. |
||||
This section uses a Guid to identify the package that provides the command defined inside it. --> |
||||
<Commands package="guidILSpyAddInPkg"> |
||||
<!-- Inside this section we have different sub-sections: one for the menus, another |
||||
for the menu groups, one for the buttons (the actual commands), one for the combos |
||||
and the last one for the bitmaps used. Each element is identified by a command id that |
||||
is a unique pair of guid and numeric identifier; the guid part of the identifier is usually |
||||
called "command set" and is used to group different command inside a logically related |
||||
group; your package should define its own command set in order to avoid collisions |
||||
with command ids defined by other packages. --> |
||||
|
||||
|
||||
<!--Buttons section. --> |
||||
<!--This section defines the elements the user can interact with, like a menu command or a button |
||||
or combo box in a toolbar. --> |
||||
<Buttons> |
||||
<!--To define a menu group you have to specify its ID, the parent menu and its display priority. |
||||
The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use |
||||
the CommandFlag node. |
||||
You can add more than one CommandFlag node e.g.: |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
If you do not want an image next to your command, remove the Icon node /> --> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenReferenceInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyRefGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>用ILSpy打开</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenProjectOutputInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyProjGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>用ILSpy打开输出</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenCodeItemInILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyCodeItemGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<CommandFlag>DynamicVisibility</CommandFlag> |
||||
<CommandFlag>DefaultInvisible</CommandFlag> |
||||
<Strings> |
||||
<ButtonText>用ILSpy打开代码</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
<Button guid="guidILSpyAddInCmdSet" id="cmdidOpenILSpy" priority="0x0600" type="Button"> |
||||
<Parent guid="guidILSpyAddInCmdSet" id="OpenILSpyGroup" /> |
||||
<Icon guid="guidImages" id="bmpLogo" /> |
||||
<Strings> |
||||
<ButtonText>ILSpy</ButtonText> |
||||
</Strings> |
||||
</Button> |
||||
|
||||
</Buttons> |
||||
|
||||
</Commands> |
||||
|
||||
</CommandTable> |
@ -0,0 +1,126 @@
@@ -0,0 +1,126 @@
|
||||
<?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=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> |
||||
</resheader> |
||||
<resheader name="writer"> |
||||
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> |
||||
</resheader> |
||||
<data name="110" xml:space="preserve"> |
||||
<value>ILSpy.AddIn</value> |
||||
</data> |
||||
<data name="112" xml:space="preserve"> |
||||
<value>Integration of the ILSpy Decompiler into Visual Studio.</value> |
||||
</data> |
||||
</root> |
@ -0,0 +1,7 @@
@@ -0,0 +1,7 @@
|
||||
<?xml version="1.0" encoding="utf-8"?> |
||||
<PackageLanguagePackManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011"> |
||||
<Metadata> |
||||
<DisplayName>ILSpy</DisplayName> |
||||
<Description>可以在Visual Studio中直接打开反编译工具ILSpy.</Description> |
||||
</Metadata> |
||||
</PackageLanguagePackManifest> |
Loading…
Reference in new issue