Bolufer Blog - SharePoint & .NET language

Introducción a NLB con Terminal Services NLB distribuye el tráfico entre varios servidores mediante el protocolo de red TCP/IP. Puede usar NLB con una granja de servidores de Terminal Server para escalar el rendimiento de un servidor de Terminal Services distribuyendo las sesiones entre varios servidores. El Agente de sesiones de Terminal Services (Agente de sesiones de TS), incluido en Windows Server® 2008 Standard, Windows Server 2008 Enterprise y Windows Server 2008 Datacenter, realiza un seguimiento de las sesiones desconectadas en la granja de un servidor de Terminal Server y garantiza que los usuarios se vuelvan a conectar a dichas sesiones. Además, el Agente de sesiones de TS permite equilibrar la carga entre servidores de Terminal Server de una granja. La característica de equilibrio de carga del Agente de sesiones de TS proporciona esta funcionalidad. No obstante, esta característica de equilibrio de carga basada en sesiones necesita un mecanismo de equilibri

You may be wondering where to find Microsoft.SharePoint.ApplicationPages.dll , if you are creating a new SharePoint application page? But don’t worry, it resides in  _app_bin  folder of your SharePoint site’s virtual directory. Assuming your IIS inetpub is at C then the exact path of Microsoft.SharePoint.ApplicationPages.dll is C:\Inetpub\wwwroot\wss\VirtualDirectories\<Your Virtual Server >\_app_bin\Microsoft.SharePoint.ApplicationPages.dll Here is the full list of assemblies at  _app_bin  folder: Microsoft.Office.DocumentManagement.Pages.dll Microsoft.Office.officialfileSoap.dll Microsoft.Office.Policy.Pages.dll Microsoft.Office.SlideLibrarySoap.dll Microsoft.Office.Workflow.Pages.dll Microsoft.Office.WorkflowSoap.dll Microsoft.SharePoint.ApplicationPages.dll STSSOAP.DLL Creating SharePoint-like Custom Dialogs When working with SharePoint you certainly configured a  Content Query Web Part . Never wished that you could reuse this dialog from within y

If you want to display a table (or a view or a stored procedure) data from your SQL Server database in your SharePoint 2010 which resides in a different server, these are the steps that you can take:  1. Create a Secure Store Service (SSS) using SharePoint 2010 Central Administration as shown below: First select “Manage Service Application” Then select Secure Store Service And follow the Wizard instructions. For the purpose of this simple example select the default values. Then set the credentials for the SSS. Let’s call this SSS_1. 2. Create an External Content Type (ECT) using SharePoint Designer as shown below: For External System choose SQL Server :  You can choose tabels, view or stored procedures for your data source. For External System Authentication Mode select “Impersonate Windows Identity” and then select SSS_1 that you set up earlier for the Secure Store Application ID as shown below: 3. After creating an ECT, there will be a Business Data Connectivity Service (B

Abstract:  With the External Content Types feature provided in SharePoint 2010, communication between two systems can be achieved easily. By using SQL Server as Data Source, you can minimize writing explicit code for database connectivity and perform CRUD operations too. As a SharePoint 2010 developer, I have come across various requirements from clients on connecting to external data sources e.g. Direct Connectivity to Database, Windows Communication Service (WCF) and External .NET type from a SharePoint Web Site. By considering its need in portal development, I decided to pen down my thoughts on this topic. This article is a result of the same. Practically there are many scenarios when a SharePoint site needs to connect to an external system which stores data inside it. E.g. A Payroll system which calculates salary of the Employee in the organization wants to communicate with a Leave Management and Processing portal for calculating total leaves of Employee. To do this in Sha