I: Visual Studio 2017 change of compiler tools directory layout

Hey @kbilsted

I just had to reinstall my machine and with it I updated/installed the newest Visual Studio version 2017. Unfortunately, they made a bigger change in the folder structure. You can read more about it here https://blogs.msdn.microsoft.com/vcblog/2016/10/07/compiler-tools-layout-in-visual-studio-15/

By that, the DllExportTask property

LibToolPath="$(DevEnvDir)\..\..\VC\bin"

won’t work anymore, as the Dev Environment changed.

I circumvented this for now by importing the current tools version props

<Import Condition="Exists('$(DevEnvDir)\..\..\VC\Auxiliary\Build')" Project="$(DevEnvDir)\..\..\VC\Auxiliary\Build\Microsoft.VCToolsVersion.default.props" />  

and set the LibToolPath to

LibToolPath="$(DevEnvDir)\..\..\VC\Tools\MSVC\$(VCToolsVersion)\bin\Host$(Platform)\$(Platform)"

You may checkout https://github.com/nea/MarkdownViewerPlusPlus/blob/master/MarkdownViewerPlusPlus/MarkdownViewerPlusPlus.csproj#L280.

I am not 100% convinced by what I did, especially with the host platform… but it works for now ^^’ If something like that with 2017 comes up on your end.

Cheers

[jokedst]

Ok, by simply removing the LibBoolPath attribute on the DllExportTask in NppPlugin.DllExport.targets it works for me in both VS2015 and VS2017. 😛

[kbilsted]

is the 2017 working for you yet? Just got a new machine, installed the pluginpack and VS2017 and seems to be working here (the v0.94.00 release from today).