New answers tagged

0

Download Telerik Just Decomplier from here http://www.telerik.com/products/decompiler.aspx Copy the WSP and change one of the copies WSP extension a CAB extension. Copy all of the files to a directory. Decompile the Dll and save it to a project. In visual studio 2013 ultimate create a new sharepoint project from an existing project and use the unchanged ...


0

I ended up trying to repair my install of Sharepoint Foundation 2013. Did not work. However I uninstalled Sharepoint Foundation and reinstalled it and my problem was fixed. Thanks for all the helps.


1

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.


0

Using Elements.xml to provision the webparts ended up working. You still need to use an XsltListViewWebPart, though you add it through a AllUserWebPart. There is a property of the XLVWP that accepts a default view, list name, etc.


0

In SharePoint 2013 there is no need to use alter the task. Directly access the list Workflow Tasks and update the item. Following code worked for me: using (SPSite _site = new SPSite(spSiteURL)) { using (SPWeb _web = _site.OpenWeb()) { ...


0

No. there won't be any impact on your SP infrastructure. VS 2012 ULTIMATE/PROFESSIONAL is just a tool/IDE to enable a smooth SharePoint development experience. Using VS Versions, you would be developing SP solutions as packages [.wsp files], and using PowerShell or stsadm command line tools you would deploy on the SharePoint farm.Without VS, you wont be ...


0

I finally resolved it, hope it helps in the future: when you setup your environment for add-ins (apps) development and you will face the same issue, remember, you have to create a ROOT site collection. After i reviewd ULS logs I realized that missing components are supposed to be stored in the root. I always created ex.: http://SPDevServer/sites/dev/ but I ...


0

I faced the kind of similar issue today, the problem was in the Custom page layout.. I was using <SharePointWebControls:FieldValue to render the HTML field.. I replaced it with <PublishingWebControls:RichHtmlField and the Web Parts started showing on the page.


1

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 ...


1

Client Object Model(CSOM) is a new feature of SharePoint 2010. It provides features to program against a SharePoint site using .NET Managed Code or JavaScript. The Client Object Model provides almost all the programming features of the Server Object Model plus advantages in deployment. The Client OM (Client Object Model) is being used as the core ...


0

Open package.package , in the bottom switch to advanced tab. Click add. Below screen will popup. Fill the required details. This way,you can add external assemblies to your wsp. This post will help to understand more.


1

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 ...


2

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 ...


2

You must perform a reset on sptimerv4 between retractions in order to unload the GAC'ed custom developed binaries.


10

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.



Top 50 recent answers are included