Getting the error below in your eventlog and do you have multiple identities for your website (i.e: sample.domain.tld & localhost)?

Event Type:        Error
Event Source:     System.ServiceModel 3.0.0.0
Event Category: WebHost
Event ID:           3
Date:                 16-9-2009
Time:                 8:46:15
User:                  NT AUTHORITY\NETWORK SERVICE
Computer:          COMPUTERNAME
Description:
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/40535505
Exception: System.ServiceModel.ServiceActivationException: The service '/Sample/SampleService.svc' cannot be activated due to an exception during compilation.  The exception message is: This collection already contains an address with scheme http.  There can be at most one address per scheme in this collection.

You could solve this issue by adding the following config section to your web.config:

    <system.serviceModel>
        ...
        <serviceHostingEnvironment>
            <baseAddressPrefixFilters>
                <add prefix="http://sample.domain.tld/Sample/"/>
            </baseAddressPrefixFilters>
        </serviceHostingEnvironment>
        ...
    </system.serviceModel>

After reading the following blog post I became curious if I could reproduce the same behavior on the HashSet.

So what did I do. I tested an List, Dictionary and a HashSet.

For all types I ran the test five times. Every run I added 10.000 items. Besides adding items to the collection I checked if the collection contained the item. This test I did 5 times with 10.000 items in the collection to check.

The figure show the result for adding the items to the different collections, and checking if the collection contained the item.

The horizontal line shows the amount of milliseconds to Add or check if the item contains in the collection. Without having a look at the numbers it is obvious that the Contains method on the List collections is slower than the Contains method on the HashSet or the Containskey on a Dictionary. The difference can be explained because the HashSet collection as well as the Dictionary collection uses a hashing algorithm to quickly retrieve data from it’s collection.

To get an better view on the time it takes to add an item to the different collection and see which collection is faster for retrieving the data, I removed the data duration data from the List Contains method is the graph below.

The graph shows that the HashSet is slower to do an lookup than the Dictionary. To be precise, it took the double amount of time to check every single item if it was in the collection. For adding stuff the List collection was the absolute winner. If we compare both structures who uses the a hashing table, the HashSet was the absolute winner. It took the Dictionary object 37,5% longer to add 10.000 items.

Even Stian Sveen got a lot of complains about his post. I got exactly the same result as he did. Until somebody else proven otherwise I believe that a Dictionary collection is faster for retrieving items than a HashSet when the collection contains 10.000 items.

A while ago a friend a my promoted ELMAH via Live messenger, since then I am a FAN! ELMAH (Error Logging Modules and Handlers) is an application-wide error logging facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.

Exceptions caught by ELMAH can be stored in memory, loose xml, VistaDb, Access, SQLLite, Oracle, MS Sql, or directly send by email. Storage- & mail configuration is done via the web.config.

The source of ELMAH is available and under the Apache License 2.0.
More info @: http://code.google.com/p/elmah/

In this post I’ll do an new implementation of the ELMAH Errorlog class to facilitate the MS SQL error logging with MOSS elevated privileges to solve the following problem.

The RunWithElevatedPrivilegesmethod will executes the specified code with Full Control rights even if the user does not otherwise have Full Control. In the MOSS environment it will execute the code under control of the the Application Pool Identity User. Implementing this method is really easy:

SPSecurity.RunWithElevatedPrivileges(delegate()
{
   // put your code in here :)
});

The first step is to setup a class in Visual Studio (my example SqlErrorLogWEP (Sql ErrorLog With Elevated Privileges) and implement the abstract Errorlog class.

namespace Elmah
{
    using System;

    class SqlErrorLogWEP : ErrorLog
    {
        public override string Log(Error error)
        {
            throw new NotImplementedException();
        }

        public override ErrorLogEntry GetError(string id)
        {
            throw new NotImplementedException();
        }

        public override int GetErrors(int pageIndex, int pageSize, IList errorEntryList)
        {
            throw new NotImplementedException();
        }
    }
}

Because our SqlErrorLogWEP looks really for 99,9% like the classic SqlErrorLog class. In fact our class will act as a wrapper to implement the MOSS elevated privileges functionality for the SqlErrorLog class. To do this our constructor will initialize the (classic) SqlError log class and use the private sqlErrror object to perform the database logging. The above methods which still need to be implemented will use the sqlError object to do the work.

Our new class will look like this:

namespace Elmah
{
    using System;
    using System.Text;
    using System.Collections;
    using Microsoft.SharePoint;
    

    class SqlErrorLogWEP : ErrorLog
    {
        SqlErrorLog sqlErrorLog;

        public SqlErrorLogWEP(IDictionary config)
        {
            sqlErrorLog = new SqlErrorLog(config);
        }

        public SqlErrorLogWEP(string connectionString)
        {
            sqlErrorLog = new SqlErrorLog(connectionString);
        }

        public override string Log(Error error)
        {
            string retVal = String.Empty;
            SPSecurity.RunWithElevatedPrivileges(delegate()
            {
                retVal = sqlErrorLog.Log(error);
            });

            return retVal;
        }

        public override ErrorLogEntry GetError(string id)
        {
            ErrorLogEntry retVal = default(ErrorLogEntry);

            SPSecurity.RunWithElevatedPrivileges(delegate()
            {
                retVal = sqlErrorLog.GetError(id);
            });

            SPSecurity.RunWithElevatedPrivileges(delegate()
            {
               // put your code in here :)
            });
            return retVal;
        }

        public override int GetErrors(int pageIndex, int pageSize, System.Collections.IList errorEntryList)
        {
            int retVal = -1;

            SPSecurity.RunWithElevatedPrivileges(delegate()
            {
                // put your code overhere 
            });

            return retVal;
        }
    }
}

Pro’s  / Con’s
Pro’s: Implementation in 2 minutes, completely ELMAH proof, extendable.
Con’s: Instead of only deploying the ELMAH assembly you will have an extra reference to the Microosoft.SharePoint assembly.

The AJAX Control Toolkit is a joint project between the community and Microsoft. Built upon the ASP.NET 3.5 AJAX Extensions, the Toolkit aims to be the biggest and best collection of web-client components available.
The Toolkit addresses three needs. First it gives website developers a place to get components to make their web applications spring to life, second it gives a set of great examples for those wishing to write client-side code, and third it is a place for the best script developers to get their work highlighted.

Version number: 3.0.30512

info: here!

As with every new release of Microsoft BizTalk, InfoSupport is setting up a DeepDive training track with a trainer coming from Redmond. I bet it is Robert or John Callaway from Quicklearn. For everybody who is interested in BizTalk these DeepDives are the place to be. 

Info: 
BizTalk 2009 Developer Deep Dive (5 dagen)
After five extended-hour days of training and intensive labs, Deep Dive attendees will leave prepared with the advanced skills required to build complete enterprise-level SOA and integration solutions using BizTalk 2009. Deep Dive attendees are guaranteed to be challenged as they use advanced BizTalk techniques to build a complex integration solution.
You can choose to complete labs using BizTalk 2006 R2, or use the latest features of BizTalk 2009, including updates for Hyper-V, improved clustering capabilities, and the enhanced BAM, EDI, and ESB Guidance 2.0!
Inschrijven en meer informatie:

Getting the following error after uninstalling version 4.0?

This version of the Enterprise Library cannot be installed side-by-side with version 4.0. Please uninstall Enterprise Library v4.0 and try again

Try to remove the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Enterprise Library v4

After part 1, part 2 has just been release before the weekend. I have to admit that I’m not completely ready with part one yet :)

What Is Ramp Up?
Ramp Up is a free, online, community-based learning program, with a number of different tracks that will help you build your portfolio of professional development skills. Ramp Up has a solid foundation of premium technical content from subject-matter gurus, and provides easy-to-access content in a variety of forms that guide you in learning the important skills. Join Ramp Up (it's free!) and help advance your career - click on a track now to start!

The following five SharePoint tracks for Developers are available at Ramp Up – Part 2:

Level 1: Page Navigation
Did you know that you can integrate your application into SharePoint’s navigation? This topic looks at how SharePoint pages are arranged into web sites. Menus such as the site actions menu, the top navigation bar menu and the edit control block menu are explained. It shows how the menus in SharePoint can be updated so that a web site built on SharePoint can be customized.

Level 2: Page Branding
Did you know that you can completely brand a SharePoint site to look like your existing web? Web applications need design and SharePoint allows for this using master pages, cascading style sheets and themes. This topic walks through how to apply these artifacts to a SharePoint site and covers the process for modifying them to achieve a web site design in SharePoint.

Level 3: Web Services
Did you know that SharePoint developers have access to SharePoint list data using built in Web Services? SharePoint allows access using code running on the SharePoint server machine and also access using web services. This topic covers use of some of the simple web services provided by SharePoint and it also shows how to create a new web service on a SharePoint machine.

Level 4: Custom Content Types
Did you know that SharePoint developers can implement different behaviors for different document types? Content types define what documents or other content types are used in SharePoint document libraries. Content types can have several SharePoint aspects associated with them including custom menus and custom processing. This topic shows how to create a custom content type and how to associate an event handler with the new content type to do data validation.

Level 5: User Management
Did you know that you don’t have to write code to manage web site users in SharePoint? SharePoint allows for end user site creation and when a user creates a site they can also manage the user permissions on that site. This topic shows how some aspects of user management are handled in SharePoint including how you can audit activities that users do and show different data depending on the role a user belongs to.

Btw: Next week MOSS Administration training in U2U  Brussels, anybody else?

Receiving the the above message while trying to test your .NET web service remotely? Try to add the follwing xml snippet in the right place of your web.config file.

<system.web>
    <webServices>
        <protocols>
            <add name="HttpGet"/>
            <add name="HttpPost"/>
        </protocols>
    </webServices>
</system.web>

happy coding :)

At this moment I'm building different kind of webparts for MOSS 2007. Some of these webparts are using the nice new fancy .Net 3.5 stuff. Because webparts are running in the SharePoint context you need to upgrade SharePoint to .Net .5 to get it to work.

Thanks to Jan Tielen I found an easy way to do this, hereby the 6-step tutorial:

• Start Visual Studio 2008.
• Create a new dummy ASP.NET Web Application Project, and make sure you target the .NET Framework 2.0 (upper right dropdown of the New Project dialog). The name of this project is not important; you won’t need it anymore when we’re done.
• Copy the web.config of your SharePoint 2007 site, into the dummy Web Application project in Visual Studio.
• Open the Project Properties in Visual Studio (right click on the Project node in the Solution Explorer, and choose Properties; or in the Project menu, select WebApplicationX Properties).
• Select .NET Framework 3.5 in the Target Framework dropdown (select Yes in the confirmation dialog).
• Copy the web.config from the Web Application Project back to SharePoint.

After doing this I did some testing inside SharePoint. Everything seemed to work. Until the next day...

The day after I needed to some things with my 'favorite tool' "SharePoint designer". I connected to my test-machine and try to open a aspx-file inside the designer (the application tree was shown as normal). I got the following error:

The server sent a response which SharePoint Designer could not parse. If you are trying to connect to a Windows SharePoint Services server, check with the server's administrator to make sure Windows SharePoint Services is installed properly.

Because I just upgraded the to .NET 3.5 , I knew the cause would be somewhere in the web.config file. After some digging  found out that inside the httpHandlers something went wrong:

<httpHandlers>
    <remove verb="GET,HEAD,POST" path="*"/>
    <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, ....."/>
    <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE),....."/>
    <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.Http....."/>
    <add verb="*" path="_vti_bin/ReportServer" type="Microsoft.ReportingServices.SharePoint.Soap.RSP....."/>
    <add verb="*" path="Reserved.ReportViewerWebPart.axd" type="Microsoft.ReportingServices.SharePoi....."/>
    <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFacto....."/>
    <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHa....."/>
    <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, ....."/>
    <remove verb="*" path="*.asmx"/>
</httpHandlers>

The <remove verb="*" path="*.asmx"/> key is removing the ScriptHandlerFactory (3 lines above) registration.

Solving is easy, move the <remove verb="*" path="*.asmx"/> key up to the top just below the <remove verb="GET,HEAD,POST" path="*"/> key. In this example your httpHandler section would look like this:

<httpHandlers>
    <remove verb="GET,HEAD,POST" path="*"/>
    <remove verb="*" path="*.asmx"/>            
    <add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler,....."/> 
    <add verb="OPTIONS,PROPFIND,PUT,LOCK,UNLOCK,MOVE,COPY,GETLIB,PROPPATCH,MKCOL,DELETE,(GETSOURCE)....."/> 
    <add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.Htt....."/> 
    <add verb="*" path="_vti_bin/ReportServer" type="Microsoft.ReportingServices.SharePoint.Soap.RS....."/> 
    <add verb="*" path="Reserved.ReportViewerWebPart.axd" type="Microsoft.ReportingServices.SharePo....."/> 
    <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFact....."/> 
    <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptH....."/> 
    <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler,....."/> 
</httpHandlers>

Making changes in the Web.config will cause the application pool to restart, don't do this in a live productional system during working hours, restartig SharePoint takes ages :)