6

这是默认的 VSPackage。我只添加了 ProvideAutoLoad 属性。

using System;
using System.ComponentModel.Design;
using System.Diagnostics;
using System.Diagnostics.CodeAnalysis;
using System.Globalization;
using System.Runtime.InteropServices;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.VisualStudio;
using Microsoft.VisualStudio.OLE.Interop;
using Microsoft.VisualStudio.Shell;
using Microsoft.VisualStudio.Shell.Interop;
using Microsoft.Win32;
using Task = System.Threading.Tasks.Task;

namespace VSIXProject1
{
    /// <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, AllowsBackgroundLoading = true)]
    [InstalledProductRegistration("#110", "#112", "1.0", IconResourceID = 400)] // Info on this package for Help/About
    [Guid(VSPackage1.PackageGuidString)]
    [ProvideAutoLoad(UIContextGuids.NoSolution, PackageAutoLoadFlags.BackgroundLoad)]
    [ProvideAutoLoad(UIContextGuids.SolutionExists, PackageAutoLoadFlags.BackgroundLoad)]
    [SuppressMessage("StyleCop.CSharp.DocumentationRules", "SA1650:ElementDocumentationMustBeSpelledCorrectly", Justification = "pkgdef, VS and vsixmanifest are valid VS terms")]
    public sealed class VSPackage1 : AsyncPackage
    {
        /// <summary>
        /// VSPackage1 GUID string.
        /// </summary>
        public const string PackageGuidString = "cca56365-4b14-4a96-9280-c30dce400195";

        /// <summary>
        /// Initializes a new instance of the <see cref="VSPackage1"/> class.
        /// </summary>
        public VSPackage1()
        {
            // 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>
        /// <param name="cancellationToken">A cancellation token to monitor for initialization cancellation, which can occur when VS is shutting down.</param>
        /// <param name="progress">A provider for progress updates.</param>
        /// <returns>A task representing the async work of package initialization, or an already completed task if there is none. Do not return null from this method.</returns>
        protected override async Task InitializeAsync(CancellationToken cancellationToken, IProgress<ServiceProgressData> progress)
        {
            // When initialized asynchronously, the current thread may be a background thread at this point.
            // Do any initialization that requires the UI thread after switching to the UI thread.
            await this.JoinableTaskFactory.SwitchToMainThreadAsync(cancellationToken);
        }

        #endregion
    }
}

看起来它没有被实例化。如果我要添加断点或 Debug.WriteLine(...) 那么什么都不会发生。当我添加命令时,什么也没有。我只能在扩展和更新窗口中看到我的扩展。

我录制了这个小视频,一步一步重现了我的问题: https ://youtu.be/B2T311Ug5FQ

我应该对我的包裹做些什么?

4

2 回答 2

13

我从默认包模板开始,对我来说,添加属性

[ProvideAutoLoad(UIContextGuids80.NoSolution, PackageAutoLoadFlags.BackgroundLoad)]

到包类使事情正常进行。尝试返回默认模板并添加该行,然后进行调试。

对我来说,这是模板中的一个错误。模板应该可以正常工作,而无需在 stackoverflow 上寻找很久才能找到神奇的缺失咒语。显然,您只想点击调试键并查看断点命中,然后从那里构建。

于 2019-04-04T17:15:06.420 回答
0

我在从 Visual Studio 2017 接管的扩展中遇到了这个问题,该扩展在通过所有中间 Visual Studio 版本接管之前,我认为可能是在 VS2010 上创建的。我改变了两件事或更多,但我不知道其中哪一个使它起作用。

  1. 类似于上面的 satnhak 必须添加

    [ProvideAutoLoad(VSConstants.UICONTEXT.SolutionExists_string, PackageAutoLoadFlags.BackgroundLoad)] [ProvideAutoLoad(VSConstants.UICONTEXT.SolutionHasMultipleProjects_string, PackageAutoLoadFlags.BackgroundLoad)] [ProvideAutoLoad(VSConstants.UICONTEXT.SolutionHasSingleProject_string, PackageAutoLoadFlags.BackgroundLoad)]

  2. 在我的 .csproj 中删除了一行

    <OldToolsVersion>14.0</OldToolsVersion>

我通过比较模板中新创建的扩展并比较所有属性(啊)找到了这些。

还发现在卸载扩展后,我必须使用另一种解决方案启动 Visual Studio 以完全完成卸载过程。我猜它在某处有一个标志,它会阻止新安装的实例化,直到它完全完成。对不起,有点模糊。

在任何情况下,还有一件好事是在这些位置记录问题:

  • %appdata%\Microsoft\VisualStudio\16.0_d1c373d5\ActivityLog.Setup.xml
  • %appdata%\Microsoft\VisualStudio\16.0_d1c373d5\ActivityLog.xsl
  • %appdata%..\Local\Temp\dd_VSIXInstaller_*.log

每个成功的实例化都会记录在最后一个实例中。

于 2021-05-24T16:00:02.957 回答