SharePoint 2007: Telerik RadEditor as default text editor

If you plan to use Telerik RadEditor as the default text editor, there are some things that are out of box and some things that need to be configured manually.

1. If you plan to use Telerik RadEditor as a web part in a page, you can edit the page and click on Add Web Part. Select the web part from the list of deployed web parts. To enable editing on the page in RadEditor, you should Edit the page.
2. I have activated two features on development KE site which enables the following: This will replace rich text editor in all edit list item pages and HTML fields.

Use RadEditor to edit HTML fields

Replace the default Rich Html editor with RadEditor (page content).

Use RadEditor to edit List Items

Use RadEditor as the default rich text editor for list items.

3. There is no automatic way to replace Content Editor Web Parts as per Telerik documentation. If you plan to replace the Content Editor Web part, you will have to follow these steps:

In existing SharePoint 2007 applications you need to manually migrate the content of the default rich-text editor Web Part to Telerik RadEditor Web Part. Unfortunately, there is no supported way of doing that automatically.

For each page where you have a rich-text editor Web Part you have to perform the following: 

1. Open the page for editing

2. Copy the content of a given rich-text editor Web Part

3. Delete this rich-text editor Web Part

4. Place a RadEditor Web Part on its place (as described in Using the RadEditor WebPart)

5. Paste to copied content inside the RadEditor Web Pard and save it

6. Repeat steps b-e for all rich-text editor Web Parts on the page

4. If you would like to customize the appearance or options of the editor, you can do that with the editor’s tools and configuration tools. You need to modify two files ListToolsFile.xml and ListConfigFile.xml located at this location on the server

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources\RadEditorSharePoint\5.6.2.0__1f131a624888eeed\Resources

FYI, SharePoint 2010 Rich text editor is much better and there would be no need to use third party editors.

SharePoint Server 2010

• BI Tools in SharePoint 2010
• Front end/visual components
• Status Indicator
• Charts
• Client and Server components
• Performance Point Service (Dashboards)
• Excel Services (Calculate from Excel docs)
• Visio Services (Process diagrams)
• Back end search components
• BI Search
• SP 2010 BI Web Parts
• Status
• KPI
• Charts
• Excel Services
• Server hosting of Excel Calculation Engine
• Browser thin client for Excel
• Excel aggregates data from multiple sources
• Exposes data using REST and JavaScript
• trusted distribution of Excel Workbooks
• users can expose Excel content in Web parts
• provides workbook data using service APIs
• IT can control parts of Excel Workbooks
• Performance Point Services
• Context driven dashboards
• provides transparency and accountability
• interactive access using browser
• created/updated by IT Professional
• Reporting Services
• not part of SharePoint
• SSRS reports built outside SharePoint can be hosted in SSRS web parts
• BI Search
• search BI Elements
• adds Excel and Reporting Services to search
• presents results based on dimensions
• links directly to specific view of the report
• BI Center Template
• predefined lists for PPS, Excel Services
• Starting point of BI Portals

SharePoint 2010: Search Enhancements

FAST Search 2010 is now part of SharePoint 2010.

	Product	Key Themes
High End	FAST Search 2010	SS 2010 + conversational user experience Enhanced content processing capabilities Deep platform flexibility and scale
Infrastructure	SS 2010	complete search experience Unique social search features Industrial strength capabilities SharePoint platform integration
Entry Level	Search Server Express 2010	Basic search experience Simple to setup and deploy FREE

 

	SS 2010	FS2010
Architecture	Index servers reads config information from the crawl DB index server crawls the content and it goes through the indexing pipeline send index + metadata to Query server + metadata database WFE sends query to Query Processor Query Processor sends to QS + Metadata database QP gets results back and sends to WFE	Two ways data can be indexed in FS2010: By using index servers of FS 2010 By using crawler of SS2010, which then uses SharePoint Connector to go send data to fast using Content API. the data does not go through any processing on SS2010 side. All processing is done at the FS2010 side. Both SharePoint and fast shares the APIs to access the query capabilities Both SharePoint and fast uses the same interface to communicate between the WFE and QP

 

.NET Connector Framework

SharePoint 2010 still supports MOSS 2007 indexing processes using Protocol handlers and BDC IDEnumerators, but SharePoint 2010 uses .NET Connectors for Exchange, Notes, Documentum, File NET, Open Text, Custom .NET Connector.

BDC based connector provides the following features:

• Support for attachments
• Item-Level security
• Crawl across entity associations
• Control the resulting display URL

Customizing User Interface

• Extend Out of Box web parts (no longer sealed)
• Add new web part that interacts with existing web parts on the search page or create custom web parts (SharedQueryManager)
• Ability to modify query before it leaves the end user page (override GetXPathNavigator method of core results web part)
• Ability to modify the search results before results are displayed to the users (this involved custom code before, now u just override AggregateResults method of LocationList class)

Custom Ranking/Relevancy models

• Admins use XML files to describe new Ranking Models
• Custom ranking models rank using a weighted-average of the features in the XML descriptor
  • Query dependent feature
  • static feature
  • click features
• manage ranking models using PowerShell
• use custom ranking model in end user using web part property
• multiple OOB ranking models
  • different for Core Results and People
  • cannot be modifed
• SharePoint 2010 search contains the following default ranking models •
  • Default ranking model •
  • Two-layer neural net model •
  • Possibly several other ranking models for people search and “Sort by Date” etc. •
• It isn’t possible to customize these OOTB models directly. •
  • Instead a template ranking model that can be edited in order to create new models. •
  • The following relevance features will only be supported in the default models: •
    • Distance •
    • Minspan •
    • Document length. •
  • These are not included in the ranking model schema that will be published as part of the Relevance OM documentation on MSDN.
  • There are 2 options for creating ranking models:
    • Starting with the “default” list of static and dynamic ingredients in the linear model by getting the template XML model and then editing and uploading the modified ranking model XML file.
    • Creating a new model in XML which conforms to SharePoint’s ranking model schema.
  • Custom ranking models are not versioned.
  • Any updates/changes to a model override the existing model.
  • Creating a new model based on the “default” and customizing it will satisfy requirements for changing weights on OOTB relevance features, similar to the SharePoint 2007 support for altering weights on managed 2010 properties.
  • However, admins will need to do the extra step of associating the model to the search results Web Parts on Web sites where they want the new ranking model.
  • Creation of a new XML model based on the schema will satisfy the requirement for specialized search applications to create a unique model targeted to their business requirements.
  • Each new release of SharePoint may contain a new version of the ranking model schema may be created.
  • In order to maintain compatibility of custom ranking models created using previous versions of the ranking model schema, the version number of the schema will be indicated using the schema version attribute.
  • New versions of the schema will retain all previous elements and attributes, although new elements and attributes may be added.

SharePoint 2010

SharePoint 2010

SharePoint 2010: Lists & Events Improvements

• Improved support for Events
• WebAdding & WebProvisioning
• ListAdding & ListAdded
• ListDeleting & ListDeleted
• Post Synchronous events
• SPEventReceiverDefinition.Synchronization (post processing after the commit of the action and before presentation with the result of the post)
• Cancel events & custom error pages
• MSF 4.0 introduces capability to cancel error and redirect user to custom error page
• Synchronous cancel with error URL
• Supported in SharePoint Browser UI only (no client support)
• WSS 3.0 events ran in context of user who triggered event, certain workflow actions were at system level
• WSF 4.0 adds event impersonation (the originating user & user token on SPEventPropertiesBase
• New Registration Capabilities
• New events registration at Site Collection Level
• SPSite & SPWeb event receiver registration via Features
• List Relationships and Joins
• Yes we now can join lists (not like a sql join)
• Set up a relationship first through a lookup field
• Projected fields
• Extra fields pulled from Parent List into view of child list
• no data is saved, it is just in view (read-only)
• show additional secondary data for presentation from parent
• Referential integrity (cascade operations)
• Select operations from both lists using LINQ (SPLinq)
• Supports LINQ, CAML, SPD 2010 (note: LINQ generates CAML under the covers)
• SPQuery.Join, SPQuery.ProjectedFields
• New Security considerations & issues
• Large List Support
• MSF 4.0 can now support 50 Million items (previously recommended 2000 for optimal performance)
• Configuration options per web application
• Admins can request privileged operations
• Two threshold (configurable using PowerShell)
• Warning threshold (2000 items)
• Throttling threshold (5000 items, error message when 5000 limit is reached)
• override query safety checks
• Normal user – 5000 items
• Super User – 20,000 items
• Configure time window for expensive queries (set time for expensive queries)
• Wide List Throttling
• SPListItem limited to 8K of data
• maximum number of joins – 6 , > 6 error is thrown
• Mark columns unique
• Unique columns must be indexed
• Existing data is validated for uniqueness
• uniqueness determined by SQL-collation (case sensitivity)
• List Item and Field Validation
• New column-level & row-level constraints on Lists & List Items

SharePoint 2010: UI Advancements

Fluency

• Office 2007 type Server ribbon
• Much better usage of real estate
• streamlined, AJAX
• one place to get to any SharePoint task
• extendible ribbon (XML)
• Multi context targeting (no need to switch betweens sites and lists)
• Dialog Framework (Modal dialog)
• supports AJAX call backs
• javascript access to dialogs
• In-Place editing
• New Status Bar (supports colors for positive, negative) and Notification area (programmatic)
• Support bulk operations (no need to select list item and perform actions on it)

New powerful webparts

• XListViewWebPart (uses XSLT)
• replaces ListViewWebPart (used CAML)
• replaces List Form (used for editing based on ASP.NET)
• Web 2.0 View Framework
• Schema agnostic
• replaces DataView/DataForm Web Part
• Better user experience
• In-Place editing (supports in SPD and Web Page)

Sites are collection of pages

• Different view forms for list actions (more add/edit/display and set default)
• pages library & assets library (no need to create images library)
• creating page is simplified
• easy Wiki linking (square brackets, javascript auto complete, intellisense)
• Word like editing (no need content editor, ribbon gives word features)
• Auto Save every minute

Master Pages

• V4.master (team  site masterpage, user content pages, _layout pages, site settings)
• minimal.master (search, office web apps, no site navigation, no ribbon, more real estate)
• simple.master (error or login pages, not customizable but can be replaced)
• default.master (backward compatible to 2007, legacy interface, no ribbon, no fluency)
• Branding application pages (central admin too)

Standards Compliancy

• Supports XHTML 1.0 support (better support for accessibility)
• Cross-Browser (IE, Firefox)

Light up user actions at list, site, site-collections.

• Add commands to common locations
• ECB
• Ribbon
• Form toolbars
• View toolbars
• Settings pages
• Add custom actions and pages (no coding, out of box)
• Much better Rich Text editor no need to use third party editors (Telerik RadEditor)

Multi-lingual support:

• No need to provision sites for each language as in 2007,
• Sites support multi-lingual, associate more than one language for the user to choose
• Limitation: List data does not support multi-lingual

InfoPath 2010

• Improved Field Picker
• List Data Connection
• Library Data Connection
• List Forms
• Custom validation
• add rules and publish

SharePoint 2010 Development using Visual Studio 2010

Developers no longer need to use the following when developing SharePoint solutions (customization):

• Limitations in Visual Studio 2008
• Visual Studio Extensions for WSS
• Codeplex tools (WSP Builder, STSDEV)
• SmartPart for running custom ascx controls
• editing manifest.xml for extensions
• building .wsp file for solution package
• manually editing CAML files

Visual Studio 2010 SharePoint Tools

• SharePoint Explorer for site exploration
• SharePoint 2010 project and item templates
• visual designers for workflows
• extensible by 3rdparty developers
• Visual web part replaces smart part ascx control development
• SharePoint Explorer
• easy way to examine site artifacts
• quick way to launch browser into site (read only treeview (can be extended) of a SharePoint site running locally)

Benefits:

• Easy build and deploy, no need to build .wsp files
• No need to mess with Rootfiles
• add own custom project templates and item templates
• add menu commands to visual studio UI

 

Compare SharePoint 2007 – SharePoint 2010 development

SharePoint 2007	SharePoint 2010
ENVIRONMENT
Windows Server 2003 or Windows Server 2008	Windows Server 2008 or 2008 R2 (Production), W4indows 7 or Vista SP2 (dev)
32 bit or 64 bit	64 bit only
.NET 3.0 (IIS 6.0 above)	.NET 3.5 and above, IIS 7.0
WSS 3.0	SharePoint Foundation 2010 (SPF)
MOSS 2007	SharePoint Server 2010
WORKLOADS OR FUNCTIONAL AREAS
SharePoint provisioning & Collaboration lists	Sites
Wikis, blogs, user profiles, my sites	Communities Social networking Enterprise metadata tagging
	Content WCM ECM DM RM
	Search Built in search FAST Search (enterprise) FAST Search Center
Excel Services SQL Reporting services Performance Point Add-On	Insights Excel Services Performance Point Services Cohesive BI integration Reporting
BDC	Composites Business connectivity services (CRUD) External content type
IMPROVEMENTS
Visual Studio 2008 (Visual studio extensions for wss 3.0 & codeplex utilities)	Visual Studio 2010 (SharePoint projects, SharePoint explorer)
.NET Framework 3.5	.NET Framework 4.0
stsadm command line	PowerShell scripts (stsadm backward compatibility)
No LINQ support (caml support)	WSS Integration with LINQ
Full HTTP Requests (postback)	Ajax requests & SilverLight support Server-side ribbon and In-Place editing
	Improvements to Lists and Events (events for child site, large lists, throttling)
no need to write CAML queries	New client object model
Workflow on lists and documents	Workflows on sites
New MOSS to access External data	External data can be accessed with SPF
SSPs	SPF support Service applications extensible Service Application architecture, Scalability
Solution Package	Sandbox Solutions and Partially trusted code, build solution and upload to site collection
	Claims based security (saml support, support Live ID)
	Developer Dashboard   request run-time length   even handlers fired   sequence of event handlers
	SPD improvements SPD objects have relationships Intuitive navigation between SPD objects SPD work migrates to Visual Studio 2010 SPD customization work exported to .wsp .wsp files imported into Visual  Studio 2010 Reusable workflows (customization) Site Workflows (Workflow designer)
	PowerShell Support Replaces stsadm powerful scripts develop custom PowerShell snap-ins (provider-based model) Microsoft.SharePoint.PowerShell

 

Terminology review (still remains the same)

Farm (SPFarm)

Web Application (SPWebApplication)

   Site Collection (SPSite)

       SPSite (SPWeb)

         List (SPList)

           Item (SPListItem)

          Document Library (SPDocumentLibrary)

             File (SPFile)

             Folder (SPFolder)

Developing with SharePoint 2010 Beta

Setup Environment:

1. Download and Install SharePoint 2010 Server on Windows 7 (64-bit)
2. Download and Install SharePoint 2010 hot fix (necessary for Windows 7, no need to uninstall SharePoint 2010)
3. Download and Install Visual Studio 2010 Beta2
4. Download and Install Office 2010 Beta (uninstall any 32-bit version office products)
5. Download and Install SharePoint Designer 2010 Beta (uninstall any 32 bit version Office products)

On Server:

Pre-requisities: Windows Server 2008 R2, SQL Server 2008 SP1, .NET 4.0 Beta