search

Wumpf / IncludeToolbox

Visual Studio extension to format, prune, and inspect include directives.
https://marketplace.visualstudio.com/items?itemName=Wumpf.IncludeToolbox
MIT License
51 stars 22 forks source link

Solution doesn't compile out of the box #62

Closed phraemer closed 5 years ago

phraemer commented 5 years ago

Hi,

would like to compile the vsix myself and try out a few changes. I cloned and tried to build Debug/Any CPU with the latest VS 2017 Can you add docs listing whatever pre-requisites are for building?

Thanks.

Dunno if this is useful but here are the errors I get.

1>------ Build started: Project: VCProjectUtils.VS14, Configuration: Debug Any CPU ------
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudio.VCProject, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.VisualStudio.VCProjectEngine, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
1>C:\b\tests\IncludeToolbox\VCProject.Base\VCHelper.cs(2,17,2,29): error CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
1>C:\b\tests\IncludeToolbox\VCProject.Base\VCHelper.cs(18,24,18,43): error CS0246: The type or namespace name 'VCFileConfiguration' could not be found (are you missing a using directive or an assembly reference?)
1>C:\b\tests\IncludeToolbox\VCProject.Base\VCHelper.cs(85,23,85,35): error CS0246: The type or namespace name 'VCLinkerTool' could not be found (are you missing a using directive or an assembly reference?)
2>------ Build started: Project: IncludeToolbox, Configuration: Debug Any CPU ------
2>C:\b\tests\IncludeToolbox\IncludeToolBox\IncludeToolbox.csproj(294,5): error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.VisualStudio.Threading.Analyzers.15.6.46\build\Microsoft.VisualStudio.Threading.Analyzers.targets.
3>------ Build started: Project: Tests, Configuration: Debug Any CPU ------
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\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.14.0, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
3>CSC : error CS0006: Metadata file 'C:\b\tests\IncludeToolbox\IncludeToolBox\bin\Debug\IncludeToolbox.dll' could not be found
========== Build: 0 succeeded, 3 failed, 2 up-to-date, 0 skipped ==========
Wumpf commented 5 years ago

I'm getting the same, looks like VS updates broke it. This is not the first time something like this happens, a never ending source of joy :(

Wumpf commented 5 years ago

@phraemer Should work now again. Hope I didn't break VS2015 support in the progress (no longer have it installed), but VS2017 seems to work fine with this now.

phraemer commented 5 years ago

Thanks! It works now!

phraemer commented 5 years ago

a never ending source of joy :(

I feel your pain.