Hot answers tagged visual-studio
Running Build in Visual Studio will generate/create the assembly. Deploying it will simply register it with the SharePoint platform. Update: As David added, the "Deploy" command in Visual Studio does also trigger the build event before it is deployed to SharePoint. The act of deployment within SharePoint though, simply registers it with SharePoint.
Since Visual Studio 2012 was released before the updated version of SharePoint there (were) some post install updates that had to be run. I believe at this point, everything is bundled into VS 2012 Update 2 which was released recently. http://www.microsoft.com/en-us/download/details.aspx?id=38188
First thing, You should always keep a backup of web.config and shouldn't touch it unless you know what you are doing. If your web application isn't customized then just create another web application in CA which will create a new web in IIS too a and virtual directory for it. You can copy newly created Web application's web.config to create a web.config for ...
No, there aren't plugin for SP Designer and there aren't plugin for VS to edit pages and list view as Designer does. The explanation is simple the two tools have two different focus. Designer is not for developer users instead VS is for developers that want customize heavily SharePoint.
It is available on the App Web under "The APPWEB URL"/Lists/"The list internal name" But really you should access the list (CRUD items) via Client object model or REST. The list is meant to be "hidden" to the users of the app, and it is upp to you to provide interfaces to work with items in the list And just a clarification: You need to use ...
Only top voted, non community-wiki answers of a minimum length are eligible