Bolufer Blog - SharePoint & .NET language

ERROR: No se encontró la aplicación Web en http://server. Compruebe que escribió la dirección URL correctamente. Si la dirección URL da servicio al contenido existente, puede que el administrador del sistema necesite agregar una nueva asignación de solicitud de dirección URL a la aplicación deseada. SOLUCIÓN: En mi caso, con cambiar la propiedad Platform Target a Any CPU, estaba en x86 se me conecto correctamente. Manda GUEVOS. If you want to create a Windows Form Application in Visual Studio 2010 that uses the SharePoint dll, This is what you'll need to do: 1. Create a new Windows Form Application 2. Go To "Project Properties" by right clicking the project name. 3. Make sure "Target Framework" under "Application" tab is set to ".Net Framework 3.5". 4. Make sure "Platform Target" under "Build" tab is set to "Any CPU". Click F5 and enjoy

The task of every Sharepoint developer is to provide a solution that is easy to be deployed to the end systems of the client being it development, staging or production environment. In most of the cases a real life SharePoint project has a set of custom lists, document libraries and custom pages/web parts, so covering them will make the every day life of most of you a little bit easier. In this article I will cover the approach that I found most useful for myself from a developer stand point of view. Once the VSeWSS 1.3 is being installed on the machine where Visual Studio .NET is located we get access to the Sharepoint project templates: One of the available Sharepoint templates is the List Definition which is the one we can use to create a Sharepoint list. After selecting it we will have the chance to select what kind of template we want to create: In our case we want to create a custom list, so we just have to select the Custom List base definition. However this is just a d

Sharepoint server  : 1- Poner el valor a true de <pages enableSessionState="false" 2- Ejecutar en el shell de sharepoint  Enable-SPSessionStateService –DefaultProvision Sharepoint foundation :  1- Poner el valor a true de <pages enableSessionState="false"  2 - Ir a   <system.web> y añadir     <sessionState mode="InProc" />  3- ir a  <modules runAllManagedModulesForAllRequests="true"> y añadir <add name="Session" type="System.Web.SessionState.SessionStateModule" />

In SharePoint 2010, there are two types of installations: Farm  and Standalone. If you want to install SP 2010 on a single machine, it will not allow you to install farm set up out of the box as by default it requires Active Directory which means your machine needs to join a domain where Microsoft Active Directory has been already setup. To workaround this problem for Windows Server 2008 machine, you could do the following: 1. Install SQL Server 2008 R2 Development/Enterprise edition. 2.  Install SharePoint 2010 Installation using Farm Setup. 3. Before proceeding to launch the SP2010 Configuration Wizard, open the SP2010 PowerShell and run this command: New-SPConfigurationDatabase After that, you will get the following window: Enter a Database Name (i.e SharePoint_Config_Db) Next: Enter a Database Server: (Your Database server name, if the database is hosted on the same machine, type in your machine name) After that you will get a login prompt to enter your Farm Creden

How to enable it ? To enable dashboard you need to create the Usage and Health Data Collection Service Application. Use the below powershell command to create the service application. New-SPUsageApplication -Name "Health and Usage Application" -DatabaseName "SP2013_Health_and_Logging_Database". Once you run the above command it will create the service application with the name Health and Usage Application and the respective database. Once you have created the service application you have to enable the dashboard. In the previous versions we use to get three options ON/OFF/OnDemand settings for the dashboard. Now in this version you will get only two options ON/OFF. To enable the dashboard, we will use ON setting and use the below powershell command. $svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $dds = $svc.DeveloperDashboardSettings $dds.DisplayLevel = "On" $dds.Update() After executing the above powershell com

I was doing an analysis for a client to figure out if there were any capacity improvements on the new SharePoint 2013 RTM compared to SharePoint 2010 and I thought I would put it in a chart and make it available for my blog readers. What I found was that besides the new features,  the most significant amount of changes were on the limits for Search as search has had some big underlying architecture changes for SharePoint in this release. This data is taken from the Microsoft TechNet article entitled: SharePoint Server 2010 capacity management: Software boundaries and limits as well as the article entitled: Software boundaries and limits for SharePoint 2013 .  To get more detailed information, go directly to these articles. Disclaimer : As SharePoint 2013 RTM has just been released, I’m sure there are still updates being made to the article so please refer to the TechNet articles for any more information required as well as updates. Microsoft states that some values in