Forum Discussion
We need to be able to build SharePoint 2016 WebParts with Visual Studio 2017 on Windows 10.
We need to be able to build SharePoint 2016 webparts with Visual Studio 2017 on Windows 10. How? Why do we need to have SharePoint Servers setup everywhere to build our SharePoint WebParts? Our source code needs to be security scanned (Fortify). Why do we need a Servers setup for this? We should be able to build VS projects on any computer. Up until VS 2015 we have been able to build our WebParts on a Windows Workstation, package them up and deploy to SharePoint Server. Microsoft please reply with a explanation and provide instructions on building and packaging SharePoint 2016 WebPorts using Visual Studio 2017 and Windows 10? Why is Microsoft intentionally making developer's life's miserable? It is extremly difficult to even get help from Microsoft anymore. How do we go to get help on this? Years ago it was much better. This should be a no brainer. I tried this which worked with VS 2015 and now not working with VS 2017. Development With A Dot - SharePoint Pitfalls: Creating a Visual Studio Project Without SharePoint Locally Installed (asp.net).
1 Reply
I was able to get this all to work on VS 2017 and win10:
- Follow using 16 hive for SP2016.
https://weblogs.asp.net/ricardoperes/sharepoint-pitfalls-creating-a-visual-studio-project-without-sharepoint-locally-installed
- Update registry with all settings HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0 settings from the SharePoint Server.
Saw different problem with SP project not loading with "Update Required" error.
- Update MinimumOfficeToolsVersion from 14.6 to 14.0 in the project files.
- Follow using 16 hive for SP2016.
