In our previous blog SharePoint 2013 Local Development solutions and remote debugging, we described how to modify the registry so that SharePoint 2013 solutions can be edited locally, and it is also mentioned that local creation is not possible even if you modify the registry.
Later, after a careful look at the structure of the registry, think about the possible causes of this problem, after several attempts to find a local SharePoint solution to create is also feasible. However, not all development templates can be created locally, such as event triggers, lists, workflows, etc., templates that create processes that must interact with SharePoint, and we cannot create them locally.
After testing, it is found that the following templates can be created locally:
The development of WebPart
Development of Visual WebPart
Module Deployment Master Page
Application Page Development
Development of Web site columns
Creation of feature
This conclusion is a personal test result, only for the development of reference, if there are problems need to be carefully investigation. All of the above are tested by myself, except for the above development template, which I found in the test, must be created with SharePoint interaction and we can do nothing about local creation.
1, if you want to use local VS2013 to create SharePoint solutions and projects, you need to delete the following registry node, that is, sharepointtools, remember to export the backup before you need to import again, after a period of time to use, has not found a problem with vs use.
2. If you do not modify the registry to create a SharePoint solution, you will be prompted with the following error:
3, after deleting the registry, restart VS, create a SharePoint Empty project success, as shown in the following figure: