Quantcast
Channel: Visual Studio Integrate forum
Viewing all articles
Browse latest Browse all 4410

Visual C++ Build Tools 2017 extension support missing assemblies

$
0
0

I installed the Visual Studio Build Tools 2017 (Version 15.9.17). I then selected the following workflows:

* Visual C++ build tools
* .Net desktop build tools
* Visual Studio extension development

However, when I attempt to build my Visual Studio extension using these tools, I see several warnings about missing assemblies, such as:

C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets (2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudio.Shell.Framework, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [VSPlugin.csproj]

Some of the other assemblies that the build warns are missing are:

* Microsoft.VisualStudio.OLE.Interop
* Microsoft.VisualStudio.Shell.15.0
* Microsoft.VisualStudio.Shell.Framework
* Microsoft.VisualStudio.Shell.Immutable.10.0
* Microsoft.VisualStudio.Shell.Interop
* Microsoft.VisualStudio.Shell.Interop.8.0
* Microsoft.VisualStudio.Shell.Interop.9.0
* Microsoft.VisualStudio.Shell.Interop.10.0
* Microsoft.VisualStudio.VCProject
* Microsoft.VisualStudio.VCProjectEngine

The build then exits with a code of 1, causing a failure.

As I understand it, these assemblies should be located in:

C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\PublicAssemblies

However there is only one file in that directory: Microsoft.VSSDK.TestHostFramework.dll

Why were these assemblies not installed as part of the Visual Studio extension development workflow, and how do I install them?



Viewing all articles
Browse latest Browse all 4410

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>