From 5dba4e859e2806ce74d806fbd5dda37b7fa628d5 Mon Sep 17 00:00:00 2001 From: Roy Ben-Shabat Date: Wed, 16 May 2018 13:57:15 +0300 Subject: Improved Tango Build Engine VS Extension. Added HardwareSpeedSensor to DB Entities & PMR. Added progress to proto folder compiler. --- .../TangoBuildCommandPackage.cs | 75 ---------------------- 1 file changed, 75 deletions(-) delete mode 100644 Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs (limited to 'Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs') diff --git a/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs b/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs deleted file mode 100644 index f31bb8193..000000000 --- a/Software/Visual_Studio/Tango.BuildExtensions/TangoBuildCommandPackage.cs +++ /dev/null @@ -1,75 +0,0 @@ -//------------------------------------------------------------------------------ -// -// Copyright (c) Company. All rights reserved. -// -//------------------------------------------------------------------------------ - -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 -{ - /// - /// This is the class that implements the package exposed by this assembly. - /// - /// - /// - /// 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. - /// - /// - /// To get loaded into VS, the package must be referred by <Asset Type="Microsoft.VisualStudio.VsPackage" ...> in .vsixmanifest file. - /// - /// - [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 - { - /// - /// TangoBuildCommandPackage GUID string. - /// - public const string PackageGuidString = "f911efc8-1a59-4b5f-953d-d715ddd70710"; - - /// - /// Initializes a new instance of the class. - /// - 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 - - /// - /// 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. - /// - protected override void Initialize() - { - TangoBuildCommand.Initialize(this); - base.Initialize(); - } - - #endregion - } -} -- cgit v1.3.1