Tag Info

New answers tagged

0

Okay, I had an idea, and creating it as a folder, then getting the item representation of that folder, and then changing that items content type and setting all the custom fields seems to have worked. SPFolderCollection folders = docLibrary.RootFolder.SubFolders; SPFolder newFolder = folders.Add(SALAE_docLibrary.RootFolder.Url + "/foo"); SPListItem ...


0

I also added ReplaceContent="True" to each file element to overwrite the previous installed version. For example: <File Url="Communications/iNewsArticle.aspx" Type="GhostableInLibrary" IgnoreIfAlreadyExists="true" ReplaceContent="true">


0

Eventually it was decided new workflows 2013 for any entirely new workflow. For those workflow based on the OOTB workflows, it will be remain in 2010 mode. Because to reproduce them isn't an easy job. And we are using VS to do the workflow because of source control purpose.


0

<?xml version="1.0" encoding="utf-8"?> <webParts> <webPart xmlns="http://schemas.microsoft.com/WebPart/v3"> <metaData> <type name="Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart, Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /> ...


0

Get it work. I replace the CreateFolder function calling by : List DocumentLibrary = clientContext.Web.Lists.GetByTitle(libName); DocumentLibrary.RootFolder.Folders.Add(sharepointFolderName); clientContext.ExecuteQuery(); And delete the two functions. I still curious why it doesn't work, but the ...


0

Since you see the titles, the web parts are correctly deployed. If it was an installation issue you would get an exception page or a safecontrol error statement. 99% chance it has something to do with your code. Add some logging, redploy the dll and review the log files. note: It might also be a good idea to insert a try-catch statement and return a proper ...


1

I'm pretty sure all content type definitions created in VS are, by default, site content types. There is no attribute in the Content Type element of a content type definition that allows you to target a specific list. Even if you were going to create a list definition declaritively in VS, to include a content type in the list you would have to create a ...



Top 50 recent answers are included