Tag Info

New answers tagged

0

i dont get what your tryinh todo? the first method is correct the second you cant add namespace and assembly. aspx: <%@ Register Src="~/_controltemplates/15/InfoTable-SP2013WebPart/UserControl1.ascx" TagPrefix="uc1" TagName="UserControl1" %> ... <uc1:UserControl1 runat="server" id="UserControl1"></uc1:UserControl1> so the issue lies ...


0

I experienced similar symptoms within an VS2012 project targeting SP2010 after I separated some code into a new class library within the VS solution. After separating the code, I could no longer get the automatic pre-deploy build to run in the correct order. I tried everything in this thread. But I stumbled into a solution. Normally I right-click on the ...


0

Well, I see two possible ways for doing this. First: Try to convince your client to launch a very simple powershell script for activating the solution throughout the mysite web application. You can give the script to their administrators for them to analyze and run if they're set on it. Second: If you're REALLY set on not using powershell. Edit the ...


2

It is really simple. The best way is creating an External list using Visual Studio. Here is a service class I wrote. public partial class BlogArticleService { private const string FeedUrl = "http://blogs.microsoft.com/feed/"; private const string DateDisplayFormat = "MM-dd-yyyy"; private static List<BlogArticle> blogArticles = new ...


2

if this helps anyone, this code returns the values I needed. List listFields = context.Web.Lists.GetByTitle("Financial Notes"); context.Load(listFields); context.Load(listFields.ContentTypes); context.Load(listFields.Fields); ListItem item; // this is how you can get the item(file), you can also use CAML query context.Load(item = ...


3

This error occurs since requested properties have not been loaded. You have to explicitly specify them in ClientRuntimeContext.Load method. Since you are getting ListItemAllFields property, you have to specify like this: context.Load(listItem, i => i.File,i => i.File.ListItemAllFields); Example 1 In order to retrieve File object with all List Item ...


1

Do you want to retrieve the properties? If yes, then you will find it within your SPListItem -> listItem["Modified_x0020_By"], etc.. But not all of them. Via listItem.File.Versions you get a collection of the file versions which you can iterate through respectively can read the properties e.g. "Level" (Draft, Published...) or "VersionLabel" (-> version ...


2

Use File.OpenBinaryDirect method to downloads the specified file from a SharePoint site. The following example demonstrates how to download file from a Library by providing its item Id. Example /// <summary> /// Download file from a Library /// </summary> /// <param name="context">CSOM context</param> /// <param ...


0

For those interested, I found that the only real option is to use a 2010 workflow within SPD 2013 as thats the only way of accessing the 'Copy Item Extended' option which to my amazement is not present within 2013 workflows at all. Further details can be found under the following link. social.msdn.microsoft article


0

The SharePoint Dlls are referenced into your solution from 14 hive ISAPI folder. Have you tried copying the SharePoint 2013 Dll (Version 15.0.0.0) to a local folder and referencing it in your solution? If that doesnt work, can you push the same in GAC as well. Give it a try. For the moment just forget about 14 hive. Your solution should build.


0

At the very least VS2012 will update your solution file with lines like this: Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 2012 As for the rest of your solution/projects, what gets "migrated" depends on a number of factors - if you have SP1 for VS2010 then you will have far better interoparebility between the two editions of ...


1

To get the created by, you first need to get AuthorID. After that you need to use LookupSPuser to get the name of the user from the ID. For getting the Title, in entity type : List item of "Your list name". You should get the Title property.


0

The problem was with workflow manager configuration. Reconfiguring it again resolved the issue. Also, since the SharePoint version was updated from RTM to March 2013 Public Update, i had to register the workflow service again. Reference http://www.andrewconnell.com/blog/Updates-For-SP2013-Workflow



Top 50 recent answers are included