none
Has Visual Studio 2017 been tested against Windows IoT and does it work. Release notes for VS2017 seem to be incorrect

    Question

  • NOTE: This is a repost from the IoT Forum


    I read the VS2017 release notes which indicate the Windows for IoT as a target should be fine. Being adventurous I decided to download and install VS2017 to try to get the benefit of the new feature set.

    Problems that I have encountered:

    1. Despite the claim in the release notes that the IoT SDKs etc. for VS2017 are presented on the IoT site, they are not. I could find no way to load any of the IoT Templates etc into VS2017. I kept getting the message, you have already installed these Templates in VS2015. If you are supposed to uninstall VS2015 before installing VS2017 that should be in the release notes! If not then either existing VS2015 configuration options should be migrated to VS2017 or the IoT site needs to be updated to correlate with the VS2017 release notes :-).

    2. So after having builds fail and not being able to make use of my IoT projects in 2017 I decided to uninstall VS2017 and it managed to break my VS2015 installation. Basically the VS2015 tool chain is now corrupted and I get the error:

     error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 build tools.  Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". Now I need to figure out how to undo the need to have the 141 tool set or install them. "Retarget Solution" doesn't work.


    StCroppe

    Saturday, November 19, 2016 11:52 AM

Answers

All replies

  • Hi StCroppe,

    Welcome to MSDN forum.

    According to your description, you issue is more related to visual studio general questions, our forum is to talk about the installation of visual studio, I will move your thread to Visual Studio Development  > 

    Visual Studio General Questions for a professional support. Thank you for understanding.

    Best regards,

    Joyce


    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.

    Monday, November 21, 2016 7:12 AM
  • Hi StCroppe,

    I found that two extensions for the VS2015:

    https://marketplace.visualstudio.com/items?itemName=MicrosoftIoT.WindowsIoTCoreProjectTemplates

    https://marketplace.visualstudio.com/items?itemName=MicrosoftIoT.WindowsIoTCoreProjectTemplatesforVS15

    But the second one said that it worked with VS2017, so please check that whether it is related to the specific version.

    Thanks,

    Jack


    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.

    Tuesday, November 22, 2016 8:37 AM
    Moderator
  • Hi Jack, thanks I tried these. Note the second one actually says in red "ONLY FOR USE WITHVISUAL STUDIO 15 PREVIEW 4" So no VS2017 support.

    StCroppe


    wh
    • Edited by StCroppe Tuesday, November 22, 2016 10:10 AM
    Tuesday, November 22, 2016 10:10 AM
  • Hi StCroppe,

    The link would be the first one in my previous link if you open it.

    Maybe I misunderstood this issue, just to make this issue clearly, what is your windows Environment?

    I know that the VS2015 has the IOT project after we install the extension in my windows 10, so one issue is that whether the Windows Iot is the project type in VS or the Windows Environment? I discuss with certain members who are familiar with this windows Environment, it seems that generally we don't install the VS in it since VS has high requirement for the CPU or others.

    If I have misunderstood this issue, please feel free to let me know.

    Best Regards,

    Jack


    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.


    Tuesday, November 22, 2016 10:23 AM
    Moderator
  • Update:

    I install the second extension tool in the VS2017 RC in windows 10 machine, I could get it like this screen shot:


     


    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.


    Tuesday, November 22, 2016 10:53 AM
    Moderator
  • Brilliant! Thank you Jack. Do you have VS2017 installed along side VS2015? This also proved to be an issue when trying to open and build pre-existing projects.

    StCroppe

    Tuesday, November 22, 2016 2:25 PM
  • Hi StCroppe,

    You are welcome:)

    If the replies are helpful for you, please mark them as the answers, so it could help other community members.

    >>Do you have VS2017 installed along side VS2015? This also proved to be an issue when trying to open and build pre-existing projects.

    I have a windows 10 machine with these two VS versions, but sorry for that I'm not very sure that what the current issue is, do you mean that you get certain issue if you use the VS2017 to open the VS2015 project or others?

    If the previous issue is about that extension tool setup/usage in the VS2017 RC, it would be better for us to open a new thread for the project merge issue in two VS versions, would you mind opening a new thread in this forum? I will follow up it in time. Please also share us the detailed information about the new issue.

    Sincerely,

    Jack


    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.

    Wednesday, November 23, 2016 2:28 AM
    Moderator
  • Hi Jack:

    Following your suggestion I have managed to reinstall VS2017 and get some templates loaded.

    The thing that proved to be a challenge was the Mobile Emulator package that doesn't want to install and generates an installation error. So I removed this and all Android related elements from my installation check list and things seem to be working now.

    Thanks


    StCroppe

    Wednesday, November 30, 2016 2:00 PM