Bolufer Blog - SharePoint & .NET language

En la siguiente URL se dispone de todas las actualizaciones para SharePoint 2010/13/16 https://docs.microsoft.com/es-es/officeupdates/sharepoint-updates

SQL Aliases  are optional ( but recommended ), and are a great way to configure your SharePoint environment. They allow for flexibility in case the SQL instance is changed, or the server names/IPs change then it’s possible to only “ re-point ” to the new servers. This way, there’s no need to reinstall SharePoint for the new server/instance. SQL Aliases are  configured on each SharePoint Server . This is very important to remember! Let’s dive in and configure our aliases. Run  cliconfg  utility on SharePoint Server On Windows Server 2012 R2 & Windows Server 2016, we have an utility called  cliconfg . There are 2 versions:  32-bit and 64-bit. In this blog post, we will be installing the  64-bit version  ( 32-bit would be for apps compatibility, and located at C:\Windows\SysWow64 ) Log into the SharePoint Server Browse to  C :\Windows\System32 Double-click on  cliconfg cliconfg utility location When the...

Equivalencias de herramientas:  Para poder trabajar con  SPFx  (SharePoint Framework) deberemos tener configurados una serie  pre-requisitos  antes de trabajar.   NodeJS Instalaremos  NodeJS  en la version Long Term Support (LTS). OJO: Instalar la versión 8.X: https://nodejs.org/dist/latest-v8.x/node-v8.16.1-x64.msi Yeoman y Gulp Abriremos una consola de comandos y escribiremos los siguientes comandos: npm install -g yo gulp windows-build-tools Abriremos una consola de comandos y escribiremos los siguientes comandos: npm install -g --production windows-build-tools Install Yeoman SharePoint generator Abriremos una consola de comandos y escribiremos los siguientes comandos: npm install -g @microsoft/generator-sharepoint Editor de código fuente Visual Studio Code Desde la página oficial descargaremos el   Visual Studio Code Versiones de UI Fabric según SPFx SharePoint Framework v1.7.0 release uses Fabri...

While exploring SharePoint 2013, I decided to configure my SharePoint 2013 environment in order to be able to use apps from the SharePoint store, and also use advanced Service Applications, such as Machine Translation services. As you know, there is not a lot of documentation on SharePoint 2013 yet, so I decided to post the two errors I encountered during the setup, with their fixes! I used the  Technet Guide   to configure my farm, however I am working on a  Step by Step guide  with Screen Shots and detailed information to help you get it down on the first try. (Will be out 18 February 2013) Error 1.   Let’s Try this again… Everything is fine, but we had a small problem getting your license. Please go back to the SharePoint Store to get this app again and you won’t be charged for it. If ‘Retry’ doesn’t work, return to your site and try again later. Let’s try this again This is just an error because ...

In this post we will see the various steps required to configure the environment for SharePoint 2016 apps. SharePoint App Store For viewing the SharePoint app store, select  Add an app  link and click on  SharePoint Store  to view all available apps. If the app environment is not configured, then you might run into an error stating that "Apps are turned off" as shown in the following figure. Following are the steps to configure the environment for SharePoint 2016 apps: 1) Create a forward lookup zone for apps 2) Link the App Domain to the SharePoint Server 3) Start the required Services 4) Create the Subscription Settings and App Management Service Applications 5) Configure the App URL’s in SharePoint 6) Test the App environment Now lets see each of the above mentioned steps in detail. 1. Create a forward lookup zone for apps SharePoint 2016 Apps have their own, isolated URLs, which are separate from the URLs of the sites where the app is being deployed to an...