log4net in sharepoint 2007

Phil Haack explains configuring log4net in asp.net 2.0 application. We can keep the configuration in the web.config, and we need to tell the log4net, that where we kept the configuration in the Application_Start() event using XmlConfiguration.Configure() menthod. In asp.net we can add a Global.asax and keep this code in Global.asax.cs.

But how can we do this in Sharepoint?

Every site collection we create in sharepoint, creates a globals.asax file and keeps in the webapp root directory. The asax files contains the following code.

<%@ Assembly Name="Microsoft.SharePoint"%>
<%@ Application Language="C#" Inherits="Microsoft.SharePoint.ApplicationRuntime.SPHttpApplication" %>

We can add a inline code in the global.asax file as follows,

<%@ Assembly Name="Microsoft.SharePoint"%>
<%@ Assembly Name="log4net, version=1.2.10.0,  Culture=neutral, PublicKeyToken=1b44e1d426115821" %>
<%@ Application Language="C#" Inherits="Microsoft.SharePoint.ApplicationRuntime.SPHttpApplication" %>
<%@ Import Namespace="log4net.Config" %>

<script runat="server">
void Application_Start(Object sender, EventArgs e)
{

// Configure log4Net, to take its configuration from the web.config file.
 XmlConfigurator.Configure();
}
</script>

or we can derive a class from SPHttpApplication and add the Application_Start() method.

Note, as i explained here you need to keep the log4net.dll in the _app_bin directory of your sharepoint webapplication.

Cheers,
Murugan G.

Creating a Custom Site Definition from an existing Site (template) : Part 1

The msdn here and other blogs are talks about creating a site definition from an existing site definition. Some time or most of the time we need to create a site definition from en existing (running) site, with all the modification done in the site. For example we may modified the home page, introduced new custom lists, include other asp pages. So there should be a way to do this.

In this post i will create a site definition from an existing (running) site. This example takes a Blank Site, but this can be applied to any site like Team Site.

1. Create a blank site using “Blank Site” Template with default settings
2. To make it simple don’t modify anything and introduce new list.
3. Generate the site definition (source) from the newly created site, using Sharepoint Solution Generator.
4. The solution generator creates the .csproj file Site Definition and other folder.
5. Create a folder called CustomBlankSiteSource, this contains all the source to generate our new custom site definition
6. We need to create a folder structure as same site template folder structure, so create a folder called 12. Inside this folder create two sub folder namely, 1033 & SiteTemplates
7. In the 1003 folder we created above, create a folder called, xml.
8. In the SiteTemplate folder we created above, create a folder called CustomBlankSite. This folder should be map with our new site definition name.
9. Create a folder, xml inside the CustomBlankSite folder.
10. Now create a xml template for the new custom site definition as follows.

   1:  <?xml version="1.0" encoding="utf-8"?>

   2:  <!-- _lcid="1033" _version="12.0.4518" _dal="1" -->

   3:  <!-- _LocalBinding -->

   4:  <Templates xmlns:ows="Microsoft SharePoint">

   5:   <Template Name="CustomBlankSite" ID="10005">

   6:      <Configuration ID="1" Title="Customized Blank Site" Hidden="FALSE" ImageUrl="/_layouts/images/blankprev.png" Description="A customized blank site to experiment site definition from Site Template (existing site)" DisplayCategory="Custom Site Definitions" AllowGlobalFeatureAssociations="False" >    </Configuration>

   7:   </Template>

   8:  </Templates>

11. Note the template name in the above xml. This name and the folder name inside the site template should be same.
12. The id value can be anything above 10000. Refer this msdn for further info for this id.
13. Name this xml file as WEBTEMP_CustomBlankSite.XML and place it in CustomBlankSiteSource\12\Template\1033\XML folder.
14. Now we have to define the whole site definition.
15. Copy the default.aspx from the Site Definition folder, generated by the Solution Generator and place it in CustomBlankSiteSource\ 12\Template\SiteTemplates\CustomBlankSite folder.
16. Open the onet.xml from the Site Definition folder, generated by the solution generator, and remove the AllUsersWebpart. Then copy the AllUsersWebpart from the onet.xml resides in the 12hive\TEMPLATE\SiteTemplates\sts\xml folder. There are more than one AllUsersWebpart, and you can copy from anyone. Change the image url, if you want your custom image.
17. So now your folder and file structure looks like this.
    

18. Place the wspbuilder.exe and cablib.dll inside the CustomBlankSiteSource folder.
19. Now execute the wspbuilder from command prompt. Make sure that you are inside CustomBlankSiteSource folder in the command prompt.
20. This creates the CustomBlankSiteSource.wsp. if you want you can use give other name as parameter to the wspbuilder.
    

Now you have a site definition which is created from an existing site. You can stsadm to add and deploy the solution.

The next article talks about adding default list like links, tasks, and custom list specific to our site definition.[Tips: The custom list is based on the Post list available in the blog site definition]

[update]
Download the sample code from here.

Cheers,
Murugan G.

References:

• How to: Create a Custom Site Definition and Configuration
• Creating a Custom Site Definition (Part 1 & Part 2)
• Custom Site Definition with Custom Master Page for SharePoint Portal Server 2007 (MOSS 2007) and WSS 3.0
  

How do I implement client side warning/error messages in Sharepoint 2007

When you invoke Remove Users from Group menu in the Peoples and Groups (Site Actions -> Site Settings -> Peoples and Groups) without selecting any user the below warning message will be displayed.

How it is implemented. The people.aspx page in the <12hive>\ TEMPLATE\LAYOUTS, contains the following js declaration,

var noUserSelectedMsg = "<SharePoint:EncodedLiteral runat='server' text='<%$Resources:wss,people_nouserselected%>' EncodeMethod='EcmaScriptStringLiteralEncode'/>";

when we request the page the people_nouserselected string resource from wss.en-US.resx resource file is assigned to the noUserSelectedMsg. This variable later used in BtnRemoveUsersClick Js function. The Resources:wsss refers to the wss.en-US.resx file. To refer some other resource file replace the wss with your resource file.

To implement your custom resource file you can create a new assembly with you custom resource file, and keep the resx file in your C:\Inetpub\wwwroot\wss\VirtualDirectories\App_GlobalResources folder. Keep the assembly in the GAC, then declare and use as in the above example.

Cheers ,
Murugan G.