aboutsummaryrefslogtreecommitdiffstats
path: root/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs
diff options
context:
space:
mode:
Diffstat (limited to 'Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs')
-rw-r--r--Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs75
1 files changed, 75 insertions, 0 deletions
diff --git a/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs b/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs
new file mode 100644
index 000000000..f31bb8193
--- /dev/null
+++ b/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs
@@ -0,0 +1,75 @@
+//------------------------------------------------------------------------------
+// <copyright file="TangoBuildCommandPackage.cs" company="Company">
+// Copyright (c) Company. All rights reserved.
+// </copyright>
+//------------------------------------------------------------------------------
+
+using System;
+using System.ComponentModel.Design;
+using System.Diagnostics;
+using System.Diagnostics.CodeAnalysis;
+using System.Globalization;
+using System.Runtime.InteropServices;
+using Microsoft.VisualStudio;
+using Microsoft.VisualStudio.OLE.Interop;
+using Microsoft.VisualStudio.Shell;
+using Microsoft.VisualStudio.Shell.Interop;
+using Microsoft.Win32;
+
+namespace Tango.BuildExtensions
+{
+ /// <summary>
+ /// This is the class that implements the package exposed by this assembly.
+ /// </summary>
+ /// <remarks>
+ /// <para>
+ /// The minimum requirement for a class to be considered a valid package for Visual Studio
+ /// is to implement the IVsPackage interface and register itself with the shell.
+ /// This package uses the helper classes defined inside the Managed Package Framework (MPF)
+ /// to do it: it derives from the Package class that provides the implementation of the
+ /// IVsPackage interface and uses the registration attributes defined in the framework to
+ /// register itself and its components with the shell. These attributes tell the pkgdef creation
+ /// utility what data to put into .pkgdef file.
+ /// </para>
+ /// <para>
+ /// To get loaded into VS, the package must be referred by &lt;Asset Type="Microsoft.VisualStudio.VsPackage" ...&gt; in .vsixmanifest file.
+ /// </para>
+ /// </remarks>
+ [PackageRegistration(UseManagedResourcesOnly = true)]
+ [InstalledProductRegistration("#1110", "#1112", "1.0", IconResourceID = 1400)] // Info on this package for Help/About
+ [ProvideMenuResource("Menus.ctmenu", 1)]
+ [Guid(TangoBuildCommandPackage.PackageGuidString)]
+ [SuppressMessage("StyleCop.CSharp.DocumentationRules", "SA1650:ElementDocumentationMustBeSpelledCorrectly", Justification = "pkgdef, VS and vsixmanifest are valid VS terms")]
+ public sealed class TangoBuildCommandPackage : Package
+ {
+ /// <summary>
+ /// TangoBuildCommandPackage GUID string.
+ /// </summary>
+ public const string PackageGuidString = "f911efc8-1a59-4b5f-953d-d715ddd70710";
+
+ /// <summary>
+ /// Initializes a new instance of the <see cref="TangoBuildCommand"/> class.
+ /// </summary>
+ public TangoBuildCommandPackage()
+ {
+ // Inside this method you can place any initialization code that does not require
+ // any Visual Studio service because at this point the package object is created but
+ // not sited yet inside Visual Studio environment. The place to do all the other
+ // initialization is the Initialize method.
+ }
+
+ #region Package Members
+
+ /// <summary>
+ /// Initialization of the package; this method is called right after the package is sited, so this is the place
+ /// where you can put all the initialization code that rely on services provided by VisualStudio.
+ /// </summary>
+ protected override void Initialize()
+ {
+ TangoBuildCommand.Initialize(this);
+ base.Initialize();
+ }
+
+ #endregion
+ }
+}