A Krunal Jani's Blog

Let’s face it.  Nowadays, management absolutely loves BI.  Especially when there are lots of pretty charts and graphs.  The thing is I’m not a BI guy.  Cubes scare me to death.  Luckily, there is the new snazzy Chart Web Part in SharePoint 2010 that gives you some BI like capabilities.  It doesn’t allow you to drill down and pivot and do all that fancy stuff, but it does let you make some nice graphs and charts that any ordinary developer can do. To get started, first you need an Enterprise version of SharePoint 2010.  Unfortunately, I used the key that was later determined to be the wrong one which led me to reinstall SharePoint with a new key.  If you don’t have any Enterprise options available, then you will be reinstalling.  Assuming, you do have an Enterprise key, you then need to activate the  SharePoint Server Enterprise Site Collection Features . This adds the chart web part (among other things).  Then edit any page and add a Chart Web Part.  You can find it under Miscella

Programming a Timed Job The Job installed in the aforementioned paragraph does not actually work because there is no "logic" to execute. To create a new Job, it is necessary to program a new class library and add it to the Global Assembly Cache (GAC) to make the logic accessible to SharePoint. The first step is to create a new "Class Library" Visual Studio 2005 project with a suitable name, then add a reference to Windows SharePoint Services (Microsoft.SharePoint.dll) and "using" directives to Microsoft.SharePoint and Microsoft.SharePoint.Administration. The Class needs to inherit from "SPJobDefinition" and to have at least one constructor to initialize the new objects. The definition of the empty class reads: using System; using System.IO; using Microsoft.SharePoint; using Microsoft.SharePoint.Administration; namespace CountDocs { public class CountDocsJob : SPJobDefinition { public CountDocsJob() { } //public C

For the project I’m working for the moment i needed a document library with contracts. The contracts have an end date and an email alert needed to be send when this end date was received. After exploring the possibility to used a work flow created in SharePoint Designer, i abounded the idea and set looked at creating a timer job. This timer job needed to run once a day, check the contracts end date and send alerts when needed. Handy links where: Creating Custom SharePoint Timer Jobs  – Andrew Connel Running timed jobs within sharepoint But the most useful link I found was by Alexander Brütt (blog by Tobias Hertkorn). On this page  you can download a fully functioning Visual Studio Template to create a SharePoint timer job and to get a deployable .wsp file after building the project.There’s even a *.bat file to deploy the solution. Nice! I’ve created this *.bat file to easily uninstall the feature and solution when testing: stsadm -o deactivatefeature -name customTimerjob -url http:/

I thought it would be helpful to share my step-by-step procedures for manually configuring claims-based authentication in SharePoint Server 2010 using an "ASP.NET database" and corresponding membership and role providers. Note that the following TechNet article provides  some  of the steps for configuring claims-based authentication in SharePoint Server 2010 (using the LDAP provider instead of the ASP.NET SQL providers): Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010) http://technet.microsoft.com/en-us/library/ee806890.aspx I had originally intended this post to simply serve as a precursor to  my next post , but during the process of writing this post, I realized that there are many pieces lacking from the TechNet article. For example, if you use the current PowerShell script provided in the above TechNet article, you end up with a Web application that doesn't support Search (because it does not enable both Windows auth