SharePoint For Developers

I am working on the Enterprise Search so recently I got the requirement that I need to crawl the data from the CRM 2011. So for that I need to create the BDCM file. I goggled it and finally got the post on the MSDN “ Source Code from my TechEd OSP309 Session ” and start working on it. I did all the steps then I got the nasty error. Tried to degug the code the inner exception was “Error: An unsecured or incorrectly secured fault was received from the other party”. “An unsecured or incorrectly secured fault was received from the other party”.  To solve the error I did the following steps.  Download the latest CRM SDK from the MSDN.  Add the latest Reference of the following  microsoft.xrm.sdk.dll microsoft.crm.sdk.proxy.dll Change the code of the function “Util_CreateOrganizationService” having a file name EntityServices.cs (At the end of this post you will find the updated code). Project name”CRMEntityService”. Rebuild the code and redeploy the dll to the GAC.

This utility help you to update the webpart properties without modify the page manually. This script reads the data from the xml configuration and update page webpart property. To update the file we need the page name and webart id all this type of configuration store in the confg.xml file. Below is the updated code. Note: There is only one Manuel step that is you need to find the site pages as well as get the Ids of the webpart that need to modify the property. This current example only modifies the Title and Xsllink of the webpart. You will find the WebPartUtility.zip at the end of this post the zip folder contains the following two files 1. Config.xml : This file contains the all the configuration required for modify 2. PropertyChange.ps1 : This file contains all the logic. Silent feature: 1. More than one site can webpart can be modified by this script. 2. More than one page , webpart and webpart properties update at once. Config contains the IsUpd

Problem: I am deploying the layout pages using the module. Inside the zones I am adding the default web parts. The problem is one of my content editor web part contains the CSS and HTML tags. When I am deploying it the web part comes properly but html not rendered properly.   I have tried the following method to solve the problem. 1.        I have placed the html in the web part then export the content editor web part and place inside the Element.xml file. The problem is still there content not rendered property.   (Not Worked) 2.        Place the html content inside the <![CDATA[]]. I am getting the red swing line. It shows that the xml not well formatted.   Please see the bellow image.   (Not Worked)   3.        Encode the Html then placed it inside the content. Now the html rendered inside the content editor web part. I used the Html Encode tool and encode the html and place it inside the content tag. (Worked)

Overview: This post helps to implement the Telerik controls in SharePoint 2010. At the end of this post you will find the source code. This example contains the two Telerik controls Treeview [Code snippets taken from the official Telerik site] Rotator [Code snippets taken from the official Telerik site] To Implement the Telerik in SharePoint 2010. Follows the below steps Create [ Empty SharePoint Project ] and give solution name [ SharePoint2010Telerik ]. Create folder in the solution [ Assembly ]. Copy two dll [ Telerik.web.design.dll ] and [ Telerik.web.UI.dll ] (You can download two dlls from telerik official site or The sample code at the end of this post also contains the same files) Add above two dll inside the package. From the solution explorer double click to the package.package icon inside package folder. Scroll to down click to the [ advanced ] button. The Additional assemble windows open click Add button the drop menu comes click [ Add Existing Assembly… ].

Some of the new feature comes with the new version of the SharePoint 2013 version as compare with the 2010. But some of the minor changes in the UI as well as the look and feel. So I am going to show you some of the new UI feature that is in SharePoint 2013 beta version may be these UI feature still with it and removed when 2013 will released. Some the silent UI feature in the SharePoint 2013 beta You will change the left & top navigation from home page without going to the site settings. All items view some of the Shortcut menus Able to search within the list  Switched between the list views by clicking on the edit link.  Add new column Intelligent window during add new user SharePoint group. View all list item page now all the custom list and other list and libraries comes under the Add and App link. (_layouts/viewlsts.aspx page)

I have taken the screen shot of the SharePoint 2013 Central Admin pages. All options are the same apart from the some of the application services new introduced some of the services are remove from the SharePoint 2013 example the Analytically service is not a part of the SharePoint 2013 beta version. Home page of the central Admin Application Management Page  System Settings Monitoring Backup and Restore Upgrade and Migration General Application Settings Configuration Wizard Security Ribbon (Showing Login, Feedback, Help and Focus on content button) List of the SharePoint 2013 Services marked Green are the new services " Site Action " Now " Site "

Lay downs all the binaries ( download from the Microsoft Site ). Run prerequisite from the SharePoint 2013 beta version. Beta version Product key After completion the prerequisite run the SharePoint installation setup. Install SQL Server Express Edition Run SharePoint 2010  Screen shot with Detail information Downloaded SharePoint 15 binaries Active directory Service Group Installing SharePoint 2013 Server Installation finished Run SharePoint 15 Products Configuration Wizard SharePoint Product Configuration  Wizard Prompt Welcome To SharePoint screen Stop all the IIS Application Pool prompt Step to connect to the FARM (Create a new server farm) Specify the Database Settings Farm Security  Settings Configure SharePoint Central Administrator Web Application Detail information about the SharePoint configuration wizard  Performing configuration task screen SharePoint 15 customer experience screen First

During installing the SharePoint 2013 beta I am stuck while installer asked for product key so here is the SharePoint 2013 beta product key. Additional information: Available as 64-bit ISO Available in these languages: English, Japanese, Spanish Installation requires the following product key: 6RNT8-XV26M-GWH36-VMGQH-94MMH

SharePoint 2010 JavaScript Object Model JavaScript Intelligence   1. Include the following lines in at the top of the JS file. /// <reference path="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\MicrosoftAjax.js" /> /// <reference path="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\SP.debug.js" /> /// <reference path="C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\SP.Core.debug.js" /> 2. Include the following lines in at the top of the  Application Page Head <% #if SOME_UNDEFINED_CONSTANT %> < script type = "text/javascript" src = "/_layouts/SP.debug.js" > </ script > <% #endif %> < script type = "text/javascript" language = "javascript" > ExecuteOrDelayUntilScriptLoaded(test, "sp.js" ); function test

  What's new for developers in SharePoint 2013 Lay down the binaries and installed in your system. Choose the right API set in SharePoint 2013 Reference for SharePoint 2013 .NET client API reference for SharePoint 2013   JavaScript API reference for SharePoint 2013   .NET server API reference for SharePoint 2013 Start working in SharePoint 2010 Programming using the SharePoint 2013 REST service SharePoint Server 2013 Client Components SDK Training SharePoint 2013: Set of training and videos (14 modules) Developer training SharePoint 2013 Preview training material (en-US) SharePoint 2013 training for IT pros SharePoint 2013 training for developers Codes Sample Apps for Office samples on Code Gallery Apps for SharePoint samples on Code Gallery

Co-authoring in SharePoint Server 2010 addresses these issues by making it possible for multiple users to work on a document, at any time, without interfering with each other's changes. This approach streamlines many common document-collaboration scenarios. For example: Two or more authors are working on different parts of a composite document. While one author works on his section of the document, another author can work on hers, without either interrupting their work. Several authors are working on a composite slide show. Each author can add slides to the presentation and edit them, instead of working in isolation and trying to merge several documents and make them consistent all at the same time. A document is sent out to several experts and stakeholders, each of whom has some edits or additions. No user’s edits are lost, because they are all working on a central, server-stored document. Microsoft Defination Co-authoring Office 2010 and Office Web Apps products : Seve