Rincón de Héctor Calvarro
Blog sobre SharePoint, Visual Studio .NET y tecnologías Microsoft

January, 2013

  • Rincón de Héctor Calvarro

    SharePoint 2013 scenarios to take in account



    With the General Availability of SharePoint 2013, I would like to share with you some points to have a healthy and supported environment.

    The following scenarios are NOT supported

    • You install SharePoint Server 2013 in a workgroup.
    • You install SharePoint Server 2013 on a domain controller. This scenario is supported only for development configurations and not for production configurations.
    • You install SharePoint Server 2013 on Windows Web Server.
    • You install SharePoint Server 2013 on a virtual machine (VM) that uses Dynamic Memory. For more information about best practice configurations for SharePoint Server 2013 and virtual machines, go to the following Microsoft TechNet website:

    Another strong point is the Contemporary UI that renders in HTML5 for mobile browsers, between others mobile views.So, the following mobile browsers detailed in TechNet are the supported ones:


    Finally, please bear in mind that SPS 2013 is built on .NET 4.5 RTM in order to develop new .NET projects, although becasue of the new Apps development model there will be a lot of custom functionality relying on JavaScript.


    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA

  • Rincón de Héctor Calvarro

    DevCamp: crea tus aplicaciones para Office 2013 y SharePoint 2013


    ¿Qué te parecería crear soluciones para Microsoft Office y SharePoint 2013, usando tecnologías web estándar, y poder distribuirlas a millones de personas en todo el mundo desde la tienda de Office en Office.com? No te pienses mucho la respuesta, ¡ya puedes hacerlo!

    Ven a nuestro DevCamp y aprende cómo conseguirlo.

    Contenidos incluidos:

    • Creación de aplicaciones para Office
    • Creación de aplicaciones para SharePoint (Office 365 SharePoint Online)
    • Uso de tecnologías web estándar para crear aplicaciones siguiendo el modelo de aplicaciones en la nube

    Si quieres aprender más sobre las aplicaciones para Office y/o SharePoint visita dev.office.com


    El registro a este evento es gratuito, pero debes estar registrado para poder asistir. Los asistentes cargarán con los gastos de reserva y pago de su alojamiento y/o viajes. Las comidas serán provistas por la organización del evento.

    Cómo registrarte

    Para registrarte en este evento, dirígete aquí y selecciona el lugar y día que prefieras (o en los enlaces para el registro en Madrid que tienes a la derecha). Esta invitación no garantiza tu plaza, recibirás una notificación informándote sobre el estado de tu registro en menos de 5 días laborales tras la cumplimentación de tu registro. Ten en cuenta que, debido a la cantidad limitada de plazas, estas se limitan a dos por empresa.


    Madrid, día 4 de Marzo de 2013

    Madrid, día 6 de Marzo de 2013




    Arquitectos / Desarrolladores web


    Email: jumpstapps@microsoft.com

  • Rincón de Héctor Calvarro

    Supported Namespaces JavaScript Client Object model SharePoint Server 2010 & 2013



    In this day and age more and more customers are choosing to use Jquery in their customized pages and choose the JavaScript client object model in SharePoint 2010 and 2013. However, it turns out that anyone with skills can reverse engineer debugging the JavaScript client used internally by Microsoft but it shouldn't be used by customers / Developers.

    Recently a customer reported an issue we using that kind of JavaScript. The code was as follows.

    function FuncNaive1() {

            var OldCalendarNotify4a = SP.UI.ApplicationPages.CalendarNotify.$4a; /cahnge to $4b if Sp1 or later

            SP.UI.ApplicationPages.CalendarNotify.$4a = function ()          





    As you can see, the code was calling to an internal function called SP.UI.ApplicationPages.CalendarNotify.$4a and even the customer was completely arware that we should change the var to $4b if SP1 or later. The internal function code looks as following:

    Then he overwrites the function calling the old functionality and a new one created by him

    It turns out that these actions are completely unsupported. It's not expected that a developer/customer call the function SP.UI.ApplicationPages.CalendarNotify.$4a due to it's not documented in the SDK of SharePoint 2010 nor SharePoint 2013, moreover you shouldn't "override" an internal function. Another point to add it's that Microsoft is free of changing the internal functionality, as you see in the customer comment concerning the SP1

    Some months ago I talked regarding this topic in the blog http://blogs.msdn.com/b/calvarro/archive/2012/09/27/reflection-and-or-reverse-engineering-of-any-microsoft-sharepoint-version-is-not-supported.aspx  so you can check the blog entry for more info.

    In order to know what namespaces functions/methods and objects are public and supported in the SPS 2010 and SPS 2013 SDK for the JavaScript object Model, you should check the following links or the SDK:

    SPS 2010 => http://msdn.microsoft.com/en-us/library/ee552096(v=office.14).aspx

    SPS 2013 => http://msdn.microsoft.com/en-us/library/jj193034.aspx

    Kind Regards.

    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA

  • Rincón de Héctor Calvarro

    Available December 2012 Cumulative Updates for SharePoint 2010 and MOSS 2007



    It is available to download the updates regarding SharePoint 2010 December 2012 CU and MOSS 2007 December 2012 CU

    SharePoint 2010 (Build 14.0.6131.5001)


    After installing the updated you should run the SharePoint Config Wizard in every server of the farm.

    If SPS 2010 installed you must only install the SPS 2010 CU because it includes the Foundation one.

    After installing the updated you should run the SharePoint Config Wizard in every server of the farm.

    After you install this hotfix, you must restart the User Profile Synchronization Service for profile synchronization to function correctly.

    To work around this issue, follow these steps:

    1.Visit Central Administration.
    2.Click Manage Services on the System Settings section.
    3.Find User Profile Synchronization Service in the list of services and then click Stop if its status is Started. Click Start and provide the credentials to start the User Profile Synchronization Service as soon as its status is Stopped.

    For more information, see the Start the User Profile Synchronization service section in the Configure profile synchronization article in the library.

    SharePoint 2007 (Build 12.0.6670.5002)

    Warning! This update will be only install if SP3 is installed in the environment.

    Please, keep in mind that you must install them in the following order first WSS 3.0, and later MOSS 2007.

    After installing the updates you must execute the SharePoint configuration wizard in each of the servers of the farm or execute  “psconfig –cmd upgrade –inplace b2b -wait” on a cmd.


    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA

  • Rincón de Héctor Calvarro

    End of full support WSS 3.0 SP2 & MOSS 2007 SP2


    Hi all.

    I would like to let you know that today ends the full support of WSS 3.0 SP2 and MOSS 2007 including the CUs until WSS 3.0 SP3 and MOSS 2007 SP3.

    So the minimal supported versión is WSS 3.0 SP3 and MOSS SP3

    For more information, please check



    Kind Regards.

    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA.

  • Rincón de Héctor Calvarro

    PowerShell 3.0, .NET 4.0 & SharePoint 2010


    Good Afternoon

    Probably some of you ,due to any automatic update in your SharePoint 2010 servers, may notice that opening the SP 2010 Management Shell you are prompted with the following messages:

               Error: "The local farm is not accessible. Cmdlets withFeatureDependencyId are not registered."

    Moreover, it turns out executing cmdlets you are having next error:

               "Microsoft SharePoint is not supported with versión 4.0.30319.17929 of the Microsoft .Net Runtime."

    As all we may know SharePoint 2010 is bulit on .NET 3.5 that relies on .NET 2.0. So, as PowerShell 3.0 uses .NET 4.0 , the assemblies compiled on .NET 3.5 of our SharePoint 2010 are not working.

    Then, in order to solve this issue temporally you should modify the shortcut of the start menú of SP 2010 Management Shell and forcé it to use PowerShell 2.0 instead of PowerShell 3.0.

    C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe-NoExit - versión 2.0 "& 'C:\Program archivos de programa\Archivos comunes\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1'"

    For more information you can check the next KB



    Kind Regards.

    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA.

  • Rincón de Héctor Calvarro

    [Update] Operating Systems supported for SharePoint 2010


    Good morning.

    As an update to the previous post Operating Systems supported for SharePoint 2010 installations.


    I would like to add:

               - SharePoint 2010 ,until next SP2, it's not supported on any Windows Server 2012 http://support.microsoft.com/kb/2724471/en-us

               - Remember for Windows SBS 2011 installations, as in Windows SBS 2008, It's only supported the version that comes with the operatiing system, SharePoint Foundation 2010.

               - Windows 8 ,as in Windows 7, is only supported for code development installations with all the "Windows features" concerning .NET 3.5 activated and the App pools running in .NET 2.0 mode.


    Kind Regards.

    Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA.

Page 1 of 1 (7 items)