Visual Studio VS2017、VSIX:未示例化刚创建的AsyncPackage

zsohkypk  于 2022-12-19  发布在  其他
关注(0)|答案(4)|浏览(164)

这是默认的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
我应该怎么做我的包被示例化?

jqjz2hbq

jqjz2hbq1#

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

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

添加到包类使事情正常工作。尝试返回到默认模板并添加该行,然后调试。
对我来说,这是模板中的一个bug。模板应该可以正常工作,而不需要在stackoverflow上花很长时间来寻找丢失的魔法咒语。显然,你只需要点击debug键,看到断点被击中,然后从那里开始构建。

yeotifhr

yeotifhr2#

我有这个问题与扩展接管Visual Studio 2017,这是之前接管通过所有中间Visual Studio版本,我想可能是在VS2010上创建的。我改变了两件事或更多,但我不知道其中哪些使它工作。
1.与上面的satnhak类似,必须添加
[提供自动加载(VSConstants.UICONTEXT.解决方案存在字符串,包自动加载标志.背景加载)] [提供自动加载(VSConstants.UICONTEXT.解决方案具有多个项目字符串,包自动加载标志.背景加载)] [提供自动加载(VSConstants.UICONTEXT.解决方案具有单个项目字符串,包自动加载标志.背景加载)]
1.在我的.csproj中删除了一行
14.0
我通过比较从模板新创建的扩展和比较所有属性(argh)发现了这些。
还发现卸载扩展后,我不得不用另一个解决方案启动Visual Studio一次才能完全完成卸载过程。我猜它在某个地方有一个标志,阻止了新安装的扩展的示例化,直到这完全完成。抱歉,所有的都有点模糊。
在任何情况下,还需要了解的是,问题记录在以下位置:

  • %appdata%\Microsoft\可视化工作室\16.0_d1c373d5\活动日志.设置. xml
  • %appdata%\Microsoft\可视化工作室\16.0_d1c373d5\活动日志. xsl
  • %应用程序数据%..\本地\临时\dd_VSIXInstaller_*.log

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

wnvonmuf

wnvonmuf3#

我的设想是:我在VS2022中创建了一个VSIX项目,然后向其中添加了一个AsyncPackage。我没有注意到VSIX项目已经包含了另一个包。
另一个AsyncPackage同时被示例化和初始化,因此,我删除了添加的AsyncPackage并使用了先前存在的AsyncPackage,问题解决了。
我找不到任何关于它的文档,但是看起来每个VSIX只加载一个包。

cnjp1d6j

cnjp1d6j4#

现在已经是2022年了,模板还没有固定。非常高兴我在发疯短短几个小时后找到了这个帖子。
添加

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

到主AsyncPackage使它加载!

相关问题