SharePoint 2013 Out of the box Javascript Utilities

Original article from the blog SharePoint with Attitude…
— Karla Ponce —

In SharePoint 2013 JavaScript becomes an essential development skill to build SharePoint solutions, developers must be comfortable using it. We will be using JavaScript to build, customize and extend SharePoint functionality, however it makes no sense to implement custom code if SharePoint already offers a capability. There are many JavaScript functions provided by SharePoint  that we can use in our solutions, requiring less custom code from our part, here I will review the ones that I find more useful:

Seguir leyendo

Anuncio publicitario

Create Custom Login Page Mixed authentication SharePoint 2013

SharePoint Developer Blog

Hi folks,

In series of my SP2013 blogs my this blog describes how to «Create Custom Login Page Mixed authentication in SharePoint 2013«.

It is bit similar to SP2010 with a small change of the master page it inherits and sharepoint assembly version. So below is my code to achieve login functionality for «Windows Authentication» and «Forms Authentication«.

ASPX Page(Application Page):

Note: 1. Some things you must replace those are highlighted below.

2. Master page used for mixed mode login page is errorv15.master

3. I override click event of login button that default use CommandName=»Login»

4. Also you can use either  <%–<a href=»/_windows/default.aspx?ReturnUrl= or  <asp:LinkButton ID=»lbInternalUsers» … former is easy but less in control from code, later best for controlling events.

<%@ Assembly Name="Microsoft.SharePoint.IdentityModel, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="YourPageName.aspx.cs" Inherits="YourNameSpace.YourClassName" MasterPageFile="~/_layouts/15/errorv15.master" %> <%@ Import Namespace="Microsoft.SharePoint.WebControls" %> <%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register TagPrefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> <asp:Content ID="PageTitle" ContentPlaceHolderID="PlaceHolderPageTitle" runat="server">     <SharePoint:EncodedLiteral runat="server" EncodeMethod="HtmlEncode" ID="ClaimsFormsPageTitle" /> </asp:Content> <asp:Content ID="Main" ContentPlaceHolderID="PlaceHolderMain" runat="server">     <div id="SslWarning" style="color: red; display: none">         <SharePoint:EncodedLiteral runat="server" EncodeMethod="HtmlEncode" ID="ClaimsFormsPageMessage" />     </div>     <script language="javascript">         if (document.location.protocol != 'https:') {             var SslWarning = document.getElementById('SslWarning');    = ''…

Ver la entrada original 213 palabras más

FBA Configuration Manager for SharePoint 2013


Nothing really earth shattering here – the previous version of FBA Configuration Manager for SharePoint 2010 ( won’t deploy directly to SharePoint 2013 so the attachment to this post includes a new version compiled the latest version of SharePoint. It also includes the late breaking fix for random errors about the Xml node belonging to a different parent. The process for configuring FBA in SharePoint 2013 is the same as it was in 2010, so this tool still has a purpose in life.

Ver la entrada original

SharePoint 2016 is coming! ¿Qué sabemos?

Hace pocos días Microsoft confirmaba seguir teniendo la intención de lanzar la siguiente versión de SharePoint (2016) a finales de este mismo año 2015. Tal y como se veía venir, parece ser que las grandes “novedades” vendrán ligadas a la nube y más a Office 365 (donde Microsoft está concentrando la gran parte de sus recursos y esfuerzos los últimos años) y la versión online de SharePoint que no a la versión on premise.

Seguir leyendo