Blog de Jérémie Clabaut (ak MinSou)

on my new vista laptop i got this error when debugging using visual studio 2005 : webdev.webserver has exited with code zero. Also the code never stop on breakpoint.

The solution is to run visual studio 2005 as an administrator (right click on vs icon and select run as administrator). You can also specify vista to always launch the application as an administrator (right click on visual studio icon then select properties, select compatibility tab)

UPDATE : With this tips visual studio does not launch when you directly open .sln files. You also have to set the visual studio launcher selector to run as an administrator (C:\Program Files\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe)

yesterday, i decided to reinstall my windows XP OS (it became very slow).

But after Service pack 3 installation, windows XP failed to startup (freeze on window xp splash screen). It made me very crazy because i found the solution 5 hours later !!!

The problem is during the SP3 installation i kept my Western digital mybook turn on (external firewire disk). Western Digital has mentioned that you should not, under any circumstances, have the My Book drive attached to the computer during the SP3 update. I didn't know this instruction, so now what can i do because  ?

The temporary solution is to disable the 1394 connection (Control Panel / Nextwork connections), right click on the 1394 connection and select disable...

Hope this helps

MinSou

since the french version of OLW has been made available, i wanted to migrate my account (I used the english beta version). However it's not possible to migrate an english version to another language version. The only solution is to delete your account and create a new one.

The cancellation service is very difficult to find, so i give it to you : http://workspace.office.live.com/cancellation/cancel.aspx 

Last week my customer asks me if we could hide the open with windows explorer action on list actions for a specific site collection. I said him it’s possible with a feature since I ever used the HideCustomAction for site actions. I supposed this will work with list actions ...

i experienced a strange problem on IE 6.0. Some of my user alerted me that they can't access WSS website because of a javascript error.
After googling and googling i found the solution (A strange solution).
I turned OFF "Use HTTP 1.1" under IE6, Tools ->Advanced -> HTTP 1.1 settings.
Refresh the page and then
I turned ON "Use HTTP 1.1"

Finally, this solution resolved the problem

Hope it helps

One of a great evolution from asp.net 1.1 to asp.net 2.0 was the caching feature. Now WSS 3.0 using the Asp.Net 2.0 web Part infrastructure.

Here is an example that illustrate how to use caching feature in your Web Part Development.

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using System.Web.Caching;
using System.Threading;

using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;

namespace DebugWebPart
{
    [Guid("2b4622f3-2274-445c-a167-62119fda2a92")]
    public class DebugWebPart : System.Web.UI.WebControls.WebParts.WebPart
    {
        public DebugWebPart()
        {
            this.ExportMode = WebPartExportMode.All;
        }

        protected override void Render(HtmlTextWriter writer)
        {
            //A very long code to execute
            string outPutHtml = ItsVeryLong();

            // TODO: add custom rendering code here.
            writer.Write(outPutHtml);
        }

        private string ItsVeryLong()
        {
            if (this.Page.Cache["DATATOCACHE"] == null)
            {
                //no data in cache

                //simulate long execution
                Thread.Sleep(10000);
                string result = "<b>Results Data, this data was insert into cache at " + DateTime.Now.ToString() + " </b>";

                //add data to cache, data will expire every 10 minutes
                DateTime expirationDate = DateTime.Now.AddMinutes(10);
                this.Page.Cache.Add("DATATOCACHE", result, null, expirationDate, Cache.NoSlidingExpiration, CacheItemPriority.Normal, null);

                return result;
            }
            else
            {
                //Retrieve directly data from cache
                return (string)(this.Page.Cache["DATATOCACHE"]);
            }
        }
    }
}

I saw many websites that indicates the hardware requirements for deploying Windows SharePoint Services with no explanation on those specifications. But I think there is no generic response for this purpose ... The server hardware and farm topology requirements depends on your customer project (Availabily, Response time ...)

So read these 2 documents, answer the questions, and you will be able to design correcly your Windows SharePoint Services Project

http://technet2.microsoft.com/windowsserver/WSS/en/library/dcdb7f80-5d48-4b7c-9cb5-affa5f2936531033.mspx?mfr=true

Planning and architecture for Windows SharePoint Services 3.0 technology, part 1

Planning and architecture for Windows SharePoint Services 3.0 technology, part 2

Since I have changed my notebooks, Virtual PC 2004 hanging when I hit the keyboard or click the mouse. The main difference between my old notebooks and the new is the processor. The new is an intel Centrino duo... So let's googling. It was very difficult to find the solution for this problem (3 hours), but i found this :
http://support.microsoft.com/kb/899525/en-us

After requested the hotfix and applied it, my problem was resolved.

Hope this information helps.

Today, for performance reason, I decided to remove the viewState on all my dropDownlist controls.  In my webForms there are 5 dropdwnlist with 100 ListItem in each. So the ViewState is very large.... But I ran into a big problem. The dropdown will no longer restore it's selected item on postbacks ...

I found the solution into a very excellent post that explains the viewstate in details :
http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx (Part 3 : Persisting Data Cheap)

quote : "This is another source of confusion with ViewState. The reason the dropdown fails to remember it's selected item on postbacks is NOT because you have disabled ViewState on it. Postback controls such as dropdownlist and textbox restore their posted state (the selected item of a dropdown ist 'posted') even when ViewState is disabled, because even with ViewState disabled the control is still able to post its value. It forgets it's selected value because you are rebinding it in OnLoad, which is after the dropdown has already loaded it's posted value. When you databind it again, the first thing it does is throw that into the bit bucket (you know, digital trash). That means if a user selects California from the list, then click on a submit button, the dropdown will stubbornly return the default item (the first item if you don't specify it otherwise). Thankfully, there is an easy solution: Move the DataBind into OnInit: "

MinSou