Hot answers tagged visual-studio
In order to develop SharePoint Solutions (as opposed to Add-ins/Apps) you have to run SharePoint on the machine running Visual Studio and the Site you you debug on must be one hosted by that SharePoint Farm. Before you continue down this road make sure you really want to create a SharePoint Solution.
You must perform a reset on sptimerv4 between retractions in order to unload the GAC'ed custom developed binaries.
Since the question does not provide much debugging information, I will try to provide some common solutions based on my personal experience and the few hints I can get from your context. Option 1 Seem something you may get when the executing code is not up to date with your Visual Studio environment. I suggest that you try and restart the OWSTIMER process ...
I have gotten to the point now that I actually don't allow VS to push my solutions out any more. Instead I do a publish to my file system and then create a script that retracts the old solution, resets IIS and SPTimerv4 and then pushes the new solution out all via PowerShell. Run Uninstall-SPSolution then Remove-SPSolution perform the IIS and SPTimer ...
Very simple Both are used to access the SP data. CSOM Access the SP data from the client side. Code will executed in the client side not in SP server. CSOM include .Net, Java Script, jQuery, Silverlight. It required reference should included in code development, For example Microsoft.SharePoint.Client.Runtime.dll and Microsoft.SharePoint.Client.dll For ...
To resolve the error make sure that the account being used to run Visual Studio is a db_owner on the SharePoint config and SharePoint admin databases.
Only top voted, non community-wiki answers of a minimum length are eligible