Visual Studio 2017 and SharePoint 2010 projects

All replies

  • Hi Richard,

    Welcome to the MSDN forum.

    Like you found, we can only create the SharePoint 2013 and 2016 in VS 2017.

    >> it appears that VS2017 converts a SP2010 project to SP2013 or SP2016 which presumably renders it un-deployable to SP2010?

    As far as I know, if you upgrade or convert a project that created in the previous VS version in a newer version, you cannot directly open this project in the previous VS version, since some changes in this project should be compatible with the previous version anymore. For the SharePoint 2010 project, please have a look at this: Porting, Migrating, and Upgrading Visual Studio Projects and I found it describes “For SharePoint 2010, you can open the project in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1.”, so it looks like reasonable, when you open a SharePoint 2012 project in VS 2017, it will be need to upgraded to SharePoint 2013 or 2016, since the SharePoint 2013 and 2016 is the supported template type in VS 2017.

    You can back up your SharePoint 2010 projects, and make sure the “.NET Desktop Development” workload must be installed in Visual Studio 2017 for the upgrade then upgrade one SharePoint 2010 project in VS 2017 to have a try, then deploy to SharePoint 2010. Usually, VS support the backwards compatibility with previous version and reverse does not works. If you meet any issue during the deploy, please redirect to this appropriate forum: and start a new thread with your detail error information, you will get a more professional support from there, our forum is to discuss Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor. Sorry for this inconvenience and thank you for your understanding.

    Best regards,


    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

    Thursday, March 09, 2017 6:36 AM