New answers tagged visual-studio-2012
This error is due to limitation in number of variables per scope. The limit is 50. I fixed it by following this link: Detailed explanation here. Found the answer through this question
A better way to solve this without adding force is after the error happens, just leave the wsp there with the error in CA, open the SharePoint Management Shell and use the update-SPSolution command with the path of the wsp file you just added to deploy, it should also deploy itself after the update. Update-SPSolution -Identity "name wsp" -LiteralPath "path ...
Related: SharePoint object model: connect to remote server? Is it true that your app has to be on the same farm as the web app context you're trying to open in your code? Yes it is true as Amal and the link above said. If not and it's a problem with my code, what is the proper way to do what I'm attempting here? You can use CSOM, or ...
Change The console app is configured for .Net 4, any CPU. to The console app is configured for .Net 4, X64. Also, as Amal said, run the console as administrator in the same box as you have SharePoint installed. Also, Run with Elevated Priviledges in a console does nothing. RWEP only removes the Impersonation and goes back to the Account that ...
If you are using Server Side Code then your application should run from the Same FARM. Else you should use Client Side Object Model.
Top 50 recent answers are included