none
Visual Studio 2017 Extension Build Task Version Does not Match BuildTools RRS feed

  • Question

  • I have VS 2017 ver 15.0.0-RC.4+26206.0 and Microsoft.VSSDK.BuildTools ver 15.0.26201. When I create a vsix package, the app builds and deploys, but when I add a project to the source.extension.manifiest for example a Microsoft.VisualStudio.Assembly or a Microsoft.VisualStudio.ProjectTemplate I get...

    "Microsoft.VSSDK.BuildTools.15.0.26201\tools\VSSDK\Microsoft.VsSDK.targets(75,5): warning VSSDK1018: Targets version (15.0.26201.0) and build task version (15.0.26206.0) do not match.  Restarting Visual Studio could help fix this issue."

    Restarting only helps if I remove the added assembly or project template. Microsoft.VSSDK.BuildTools.15.0.26201 is the latest VSSDK BuildTools that I could find and the project is referencing this version.


    innovoCAD

    Sunday, February 19, 2017 1:45 PM

All replies

  • Hi innovoCAD,

    installing the  Microsoft.VSSDK.BuildTools.15.0.26201 package, leaves the existing import in the project file:

    <Import Project="$(VSToolsPath)\VSSDK\Microsoft.VsSDK.targets" Condition="'$(VSToolsPath)' != ''" />
    
     

    please remove it by manually and check if it works

    Best regards,

    Cole Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Proposed as answer by Phil Jollans Thursday, May 25, 2017 7:05 AM
    • Unproposed as answer by Phil Jollans Thursday, May 25, 2017 7:55 AM
    Monday, February 20, 2017 5:42 AM
    Moderator
  • Hi Cole

    at first I thought that the change fixed the problem.

    However, after removing that line, the VSIX file was no longer generated!

    Phil

    Thursday, May 25, 2017 7:57 AM