Tag Info

Hot answers tagged

28

If you double-click on the feature (NameofFeature.feature), in your solution. You'll see a properties window come up - as a window that details the title, description, scope, items in solutions, and items in the feature. In the properties window, you'll see an option titled 'Always Force Install'. By default, it is set to False. You can configure that to be ...


24

Welcome to SharePoint Stack Exchange! In your Visual Studio 2012 SP Solution: Enable Always Force Install to True in for your feature. See example below: By default, it is set to False. You can configure that to be set to True.


11

I had the same problem today. I compared the project files with an older version. In my case the Package directory (with the files Package.package and Package.Template.xml) was missing. After copying this directory back from the older version of the project and modifying the csproj file to include the references to the package directory, the error solved ...


10

You need to change the order of Additional Assemblies defined on the SharePoint package since in Visual Studio 2013, this now makes a difference. My issue (and I suspect yours) was that several of my non-SharePoint projects had dependencies on each other and had to be built in a particular order. This was not an issue in Visual Studio 2012. To change the ...


9

You can do it via the XML editor as well! Steps: Go to your Features in your project. Open the feature.template.xml file add AlwaysForceInstall="TRUE" to the below tag <Feature xmlns="http://schemas.microsoft.com/sharepoint/" AlwaysForceInstall="TRUE"> Now try to deploy the code.


7

You cannot add an event receiver through the "Add new project" dialog. What you do is create an empty sharepoint project first. Then just right click on said sharepoint project, click add new item, go to Office/SharePoint and choose Event Receiver. See my screenshot.


6

Actually Visual Studio 2010 Professional, Premium and Ultimate all allow for SharePoint development as the "Office and SharePoint development tools" are available for all (see here http://download.microsoft.com/download/4/6/E/46E8BB6C-108F-467C-9292-50EE94F117B5/download/Visual-Studio-2010-Feature-Comparison-Matrix.pdf) Same stands still with Visual Studio ...


6

I would recommend these links Setup the development environment in SharePoint 2013 : http://msdn.microsoft.com/en-us/library/ee554869.aspx Develop in SharePoint 2013 : http://msdn.microsoft.com/en-us/library/jj163085.aspx How to create a basic SharePoint hosted App : http://msdn.microsoft.com/en-us/library/fp142379.aspx First Time Configuration For Apps : ...


5

I should have checked this earlier. I made 2 empty SharePoint projects. One 2010 and one 2013 and did a compare of the different files. The only difference i could find was in the csproj file. In the SP 2013 project there is a <TargetOfficeVersion>15.0</TargetOfficeVersion> property that was not present in the SP 2010 project. I added it and ...


5

You can create a Visual Web Part for SharePoint 2013 Online. Your web part will be contained in a Sandbox Solution which you will develop locally. Once development is complete you will upload the Solution Package created by Visual Studio to SharePoint Online. Once this is done your web part will be available for use. As mentioned, development will be done ...


5

within your solution click on feature.feature and goto its properties, you should now see somthing on the lines of Always Force Install just set that to true and you dont need to do the force attribute anymore! looks like a feature wasnt retracted properly and has become a phantom! ybs has a similar issue here! Visual studio Both site collections ...


5

You need to reference following JavaScript file: <SharePoint:ScriptLink ID="ScriptLink2" name="SP.UserProfiles.js" runat="server" ondemand="false" localizable="false" loadafterui="true" /> Than you can access the User Profile Properties as follows: var personProperties; // Ensure that the SP.UserProfiles.js file is loaded before the custom ...


3

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


3

This error happens if you deploy a solution which contains a visual web part to a different web application on the same farm as the web application where it is already installed. In other words, you have two web applications, A and B on the same SharePoint farm. You want to deploy solution S which contains a visual web part to web application B, but it is ...


3

you can use this code to retrive the items from MSDN: // Starting with ClientContext, the constructor requires a URL to the // server running SharePoint. ClientContext context = new ClientContext("http:SiteUrl"); // Assume the web has a list named "Announcements". List announcementsList = context.Web.Lists.GetByTitle("Announcements"); // This creates ...


3

I assume in your example Approver is a User field type. In SharePoint 2013 CSOM SP.FieldUserValue object represents the value of a user field for a list item. The following code demonstrates how to get User Name from User field: //Get user field value var assignedToVal = item.get_item('AssignedTo'); var userName = assignedToVal.get_lookupValue(); ...


3

VS2012 (I advise updating to Update 4 version which is up to date at the time of writing this) provides a number of updates regarding SharePoint 2010 development. Some of them are: Create lists and Content Types by using new designers Create Site Columns Create Silverlight webparts Publish SharePoint solutions to remote SharePoint server Test SharePoint ...


3

Has your method the following attributes? [SharePointContextFilter] But more important. Are in your MVC application included the SharePoint context file? SharePointContext.cs and TokenHelper.cs You can find them here: http://code.msdn.microsoft.com/sharepoint/


3

When developing a high trust provider hosted app in VS, you are asked "How do you want you app to authenticate". Here you have got two options. If you are developing for on premise you can select "Use a certificate". The certificates are created in IIS. See this for more information on setting up dev environment for provider hosted apps. ...


3

Solution was: Register-SPWorkflowService –SPSite "http://localhost/yourSite" –WorkflowHostUri "https://localhost:12290" –AllowOAuthHttp had to be executed!!


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


2

Here links provide for this download http://social.msdn.microsoft.com/Forums/en-US/appsforsharepoint/thread/3da6b156-f1e0-45e6-bcd3-dfe7afa3b11a/


2

You need to have SharePoint 2010 installed on the machine you wish to do development on. However, installing SharePoint 2010 on Windows 8 is unsupported (and may or may not be supported when SharePoint 2010 SP2 is released). SharePoint 2013 remote development is only good for developing "Apps", traditional solutions still must be developed locally. I'd ...


2

Go to Central Administration -> Services on Server Check if the App Management Service and Subscription Service are started. You can use the following PowerShell to start them: Get-SPServiceInstance | where{$_.GetType().Name -eq "A ppManagementServiceInstance" -or $_.GetType().Name -eq "SPSubscriptionSettingsSe rviceInstance"} | Start-SPServiceInstance ...


2

After some research we found out that the error has to do with the length of the contents of the User Control. Once you exceed the limit of 8256 characters the User Controls won’t be parsed anymore. Compare the two images. With the contents length of 8256 characters the ascx.g.cs file is still present in the solution. Once you add another ...


2

You need to download the Microsoft Office Developer Tools for Visual Studio 2012 here. This will add the "traditional" SharePoint 2013 project options as well as the ability to create app projects for Office 2013 and SharePoint 2013.


2

Find the ID of the content type you are deriving from (in your case it is 0x0101 i.e. Document Content Type). So, make sure 0x0101 is present by examining the content type in the SharePoint UI (Site Settings > Manage Content Types). You'll get an exception (as you're getting right now) on feature activation if it's not, or the Inheritance between Content ...


2

You can not install SharePoint 2010 and SharePoint 2013 "side by side" on the same box. You must configure two separate environments for testing. Here's an MSDN link walking you through configuring remote debugging for SharePoint 2013 (and it's limitations): Developing apps for SharePoint on a remote system. Also, here's a link to walk through configuring ...


2

The Library contains the definition of the library itself, including the columns, types, indexes, views, etc., but it does not actually store items. The Instance is what handles that and is typically a single instance of the defined Library and is usually created when the feature that contains it is activated. If you are a coder, think of the Library as a ...


2

Your xsl file should be located here: c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\XSL\ To map your xsl file to this folder you need to create Sharepoint Mapped Folder. Here is explanation how to do that.



Only top voted, non community-wiki answers of a minimum length are eligible