Application Services

SharePoint Server 2013 Preview includes several services for working with data in your SharePoint sites. New for SharePoint is the Machine Translation Service, which translates sites, documents, and streams for multilingual support. SharePoint Server 2013 Preview also includes Access Services and a new data access model. For converting files and streams to other formats, SharePoint Server 2013 Preview has Word Automation Services and PowerPoint Automation Services (a new feature for SharePoint). SharePoint also provides data analysis tools, like PerformancePoint Services and Visio Services, that enable business intelligence, and powerful new features in Excel Services.

Business Connectivity Services

Business Connectivity Services (BCS) enables SharePoint to access data from external data systems such as SAP, ERP, and CRM, in addition to other data-driven applications that are exposed through WCF services or OData endpoints. BCS in SharePoint 2013 Preview has been improved and enhanced in many ways, including OData connectivity, external events, external data in apps, filtering and sorting, support for REST, and others.

Enterprise Content Management

In SharePoint 2013 Preview, you can now use .NET client, Silverlight, Windows Phone, and JavaScript APIs, in addition to the newly expanded set of .NET server managed APIs, to customize Enterprise Content Management (ECM) experiences and behavior.

Workflows

Windows Azure Workflow is a redesigned workflow infrastructure that is built on Windows Workflow Foundation 4 and brings new power and flexibility to workflow authoring in SharePoint 2013 Preview. A fully declarative authoring environment enables information workers to use SharePoint Designer 2013 Preview to author powerful workflows, and a new set of Visual Studio 2012 workflow project templates let developers access more sophisticated features like custom actions. Perhaps most importantly, Windows Azure Workflow is fully integrated with the model for apps for SharePoint. In addition, workflows execute in the cloud, not in SharePoint, which provides enormous flexibility in designing workflow-based apps for SharePoint.

Search

Search functionality in SharePoint 2013 Preview includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Additionally, there have been significant enhancements made to the keyword query language (KQL).

Social and Collaboration

New and improved social and collaboration features make it easy for users to communicate and to stay engaged and informed. The improved My Site social feed helps users keep up to date with the people and content that they care about. The new Community Site feature provides a rich community experience that lets users easily find and share information and find people who have similar interests.

Mobility

With SharePoint 2013 Preview, you can combine Windows Phone 7 applications with on-premises SharePoint services and applications, or with remote SharePoint services and applications that run in the cloud (such as those that use SharePoint Online), to create powerful applications that extend functionality beyond the traditional desktop or laptop and into a truly portable and much more accessible environment. The new mobility features in SharePoint 2013 Preview are built on existing Microsoft tools and technologies, such as SharePoint, Windows Phone 7, Visual Studio, and Microsoft Silverlight. You can create SharePoint-powered mobile applications for Windows Phone using the new SharePoint phone application wizard template in Visual Studio, which lets you create simple list-based mobile applications. You can integrate new features introduced in SharePoint 2013 Preview, such as the Geolocation field type and “push" notifications from SharePoint Server, into your mobile applications.

Core Platform Enhancements

On a broader scale, SharePoint 2013 Preview has been improved and enhanced to support the new cloud-based architecture and app-driven development framework. From the SharePoint APIs at the lowest level to connectivity to social media integration, SharePoint 2013 Preview is designed and executed to support a rich application development experience. In addition to the use of Representational State Transfer (REST) endpoints for web services, there is a broad new API for both server and client development. Remote event receivers and now supported in addition to client-side rendering.

Development Tools

The current release reflects enormous strides in optimizing the existing development tools like Visual Studio and SharePoint Designer, in addition to providing the release of newly developed web-based tool "Napa" Office 365 Development Tools for developing apps. The new unified project system in Visual Studio lets you develop apps for SharePoint, apps for Office, apps for SharePoint that include apps for Office, or apps for Office that are hosted by SharePoint. In addition to the SharePoint project templates that were provided in earlier versions, Visual Studio 2012 now includes a new app project template in the Apps folder named Apps for SharePoint 2013. Several new properties have been added to the Properties window and Properties pages to support app for SharePoint projects. Other improvements include full support for development against the Cloud App Model, including OData and OAuth support, and full support for development against the Windows Azure Workflow platform.

Familiar Programming Model using Web Standards

SharePoint 2013 Preview makes it easy for any web developer, including those who work on non-Microsoft platform stacks, to create SharePoint solutions. What makes this possible is that SharePoint 2013 Preview is based on common web standards like HTML, CSS, and JavaScript. Furthermore, implementation relies on established protocols like the Open Data protocol (OData), and OAuth.

Cloud App Model

SharePoint 2013 Preview introduces a Cloud App Model that enables you to create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint. An app has few or no dependencies on any other software on the device or platform where it is installed, other than what is built into the platform. This characteristic enables apps to be installed simply and uninstalled cleanly. Apps have no custom code that runs on the SharePoint servers. Instead, all custom logic moves "up" to the cloud or "down" to client computers. Additionally, SharePoint 2013 Preview introduces an innovative delivery model for apps for SharePoint that includes components like the SharePoint Store and the App Catalog.

What's New in SharePoint 2013

1. Cloud App Model
2. Familiar Programming using Web Standards
3. Development Tools
4. Core Platform Enhancements
5. Mobility
6. Social and Collaboration
7. Business Connectivity Services
8. Enterprise Content Management
9. Search
10. Application Services

SharePoint 2013 Beta Key

6RNT8-XV26M-GWH36-VMGQH-94MMH

SharePoint 2013 Released

HI All,

SharePoint 2013 Released By Microsoft. For more information please go through the links i had posted in my Blog.

How to Refresh the Second WebPart without using Connectable webparts.

This is a requirement in an Interview for one of my friend. First Take two user controls. In First User Control Add the Controls u want and now add the second user control as a control and write the following code in WebPart1.

Procedure:-

Add one Sample Project with Name Sample001. Now Add two Visual WebParts with Names WebPart001 & WebPart002.

In WebPart Ascx Page write the below HTML.

WebPart001 Ascx

<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="WebPart001UserControl.ascx.cs" Inherits="Sample001.WebPart001.WebPart001UserControl" %> <%@ Register src="../WebPart002/WebPart002UserControl.ascx" tagname="WebPart002UserControl" tagprefix="uc1" %> <table width="100%" cellpadding="0" cellspacing="0"> <tr> <td valign="top"> <table cellpadding="0" cellspacing="0"> <tr><td>Enter Employee ID</td><td><asp:TextBox ID="txtEmpID" runat="server"></asp:TextBox></td></tr> <tr><td>Enter Employee Name</td><td><asp:TextBox ID="txtEmpName" runat="server"></asp:TextBox></td></tr> <tr><td colspan="2" align="center"><asp:Button ID="btnSave" Text="Save"         runat="server" onclick="btnSave_Click" /></td></tr> <tr><td colspan="2" align="center"><asp:Label ID="lblErrorMessage" runat="server"></asp:Label></td></tr> </table> </td> <td valign="top"> <div id="divGrid" height="300px" style="scroll:auto;"><uc1:WebPart002UserControl ID="WebPart002UserControl1" runat="server" /></div> </td> </tr> </table>

WebPart001 Ascx Load

using System; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using Microsoft.SharePoint; using Microsoft.SharePoint.WebControls; using System.Security; using WP2=Sample001.WebPart002; namespace Sample001.WebPart001 {     public partial class WebPart001UserControl : UserControl     {         protected void Page_Load(object sender, EventArgs e)         {         }         protected void btnSave_Click(object sender, EventArgs e)         {             try             {                  SPWeb currentWeb = SPContext.Current.Web;                     SPList lst = currentWeb.Lists["Employee"];                     SPListItemCollection myColl = lst.Items;                 SPSecurity.RunWithElevatedPrivileges(delegate()                 {                     SPListItem item = myColl.Add();                     item["EmpID"] = txtEmpID.Text;                     item["EmpName"] = txtEmpName.Text;                     item.Update();                     txtEmpID.Text = "";                     txtEmpName.Text = "";                 });                 SPGridView sgv = (SPGridView)WebPart002UserControl1.FindControl("sgvEmployee");                 sgv.DataSource = myColl.GetDataTable();                 sgv.DataBind();             }             catch (Exception ex)             {                 lblErrorMessage.Text = ex.ToString();             }                   }     } }

WebPart002 Ascx

<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="WebPart002UserControl.ascx.cs" Inherits="Sample001.WebPart002.WebPart002UserControl" %> <table width="100%" cellpadding="0" cellspacing="0"> <tr> <td> <SharePoint:SpGridView ID="sgvEmployee" runat="server" AutoGenerateColumns="false"> <Columns> <asp:BoundField HeaderText="Employee ID" DataField="EmpID" /> <asp:BoundField HeaderText="Employee Name" DataField="EmpName" /> </Columns> </SharePoint:SpGridView> </td> </tr> </table>

WebPart002 Ascx Load

using System; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using Microsoft.SharePoint; using System.Data; namespace Sample001.WebPart002 {     public partial class WebPart002UserControl : UserControl     {         protected void Page_Load(object sender, EventArgs e)         {                        if (!IsPostBack)             {                 getData();             }         }         public void getData()         {             SPWeb currentWeb1 = SPContext.Current.Web;             SPList lst1 = currentWeb1.Lists["Employee"];             SPListItemCollection myColl1 = lst1.Items;             if (myColl1.Count > 0)             {                 sgvEmployee.DataSource = myColl1.GetDataTable();                 sgvEmployee.DataBind();             }         }     } }

How to validate Property of People Editor using JQuery

if($("PeopleEditorID").text()=="")
{
       alert('Validation Message');      
       return false;
}

init.js bug in SharePoint 2007 site.

To fix this bug Run Microsoft Office Diagnostic Tool in Microsoft Office.

Note:-
This bug will cause in Individual System.