tinaschrepfer on tinali
Remove use of "any" content typ… (compare)
tinaschrepfer on tinali
Merge pull request #169 from Mi… Add sample support for "any" co… (compare)
tinaschrepfer on master
Update VSSDK package and remove… Merge pull request #169 from Mi… (compare)
@lsoft Best/Recommended? Not sure - but doing it the way Mads Kristensen did it might be worth considering?
System.Threading.ThreadPool.QueueUserWorkItem()
, anymore, have a read of Cookbook for Visual Studio for more up-to-date ways of doing it
Hi everyone - question about VSIX:
We're providing packages for Visual Studio 2017 and 2019 and upon installing it takes a long time to run, moreover, it installs other components than listed in our vsixmanifest (e.g. Microsoft.Net.Core.SDK.2.1 which frequently fails to install).
@yannduran this is our dependencies section of .vsixmanifest:
<Dependencies>
<Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" Version="4.6" />
<Dependency IsRequired="false" Version="[15.0,16.0)" d:Source="Installed" Id="TestWindow.Microsoft.0771d463-d74d-4e95-aac2-39d3c7ec1f97" DisplayName="Test Explorer"/>
</Dependencies>
<Prerequisites>
<Prerequisite Id="Microsoft.VisualStudio.Component.CoreEditor" Version="[15.0,16.0)" DisplayName="Visual Studio core editor" />
<Prerequisite Id="Microsoft.VisualStudio.Component.Web" Version="[15.0,16.0)" DisplayName="ASP.NET and web development tools" />
</Prerequisites>
Not sure which one might cause VS to always attempt to install .NET Core SDK 2.1. It only happens on VS 2017 tho.
System.AggregateException: One or more errors occurred. ---> Microsoft.VisualStudio.Setup.PackageFailureException: Package 'Microsoft.Net.Core.SDK.2.1' failed to install
even if the vsixmanifest has no dependencies or prerequisites :) happens on some installations on VS 2017
@yannduran interestingly, vsix installer fails with
System.AggregateException: One or more errors occurred. ---> Microsoft.VisualStudio.Setup.PackageFailureException: Package 'Microsoft.Net.Core.SDK.2.1' failed to install
even if the vsixmanifest has no dependencies or prerequisites :) happens on some installations on VS 2017
Similar error is reported to Visual Studio Community. So make sure you have the latest version of Visual Studio 2017. Also you can try repairing or completely reinstalling the instance.