hicham Boutaleb <C'est par le bien faire que se crée le bien etre>

Blog

June 30

HOW CAN YOU DEBUG YOUR WEB PARTS

Whenever an error occurs in a web part, Microsoft Office SharePoint Server 2007 shows a generic error message. If
you want to see a detailed error message, you should open the web.config file of the SharePoint web application
that contains the web part, locate the <SafeMode> node, and set the CallStack attribute to true. If you want to
be able to see more than a generic server error message, you should locate the <customErrors> element and set
the mode attribute to Off.
You do not need to set the debug property of the <compilation> element to true to be able to debug a web
part. This setting tells ASP.NET to generate symbol tables (.pdb files) when compiling pages. Since your web part
code is contained in an assembly, you can debug the necessary .pdb files by building a Debug version of the web
part library. When the debug symbols are present, you can debug web parts by attaching to the process (an
instance of w3wp.exe).
However, if you want to be able to debug web parts by letting Visual Studio 2005 auto-attach to the process,
you do need to set the debug attribute of the <compilation> attribute to true. In that case, you also need to raise
the trust level for the SharePoint web application containing your web part to WSS_Medium or greater.
Be careful: setting the debug attribute of the <compilation> attribute to true has an undesirable side effect.
Every time you run the web part library project, a .bak copy of your web application’s web.config file is created.
The blog post “Debugging web parts – a full explanation of the requirements,” written by Maurice Prather,
discusses the previously discussed techniques in detail. The blog post can be found at the following location:
http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=60.
Whenever you are auto-attaching to a process in Visual Studio 2005, the web server is restarted in order to
recycle the w3wp.exe process hosting your web part. This is overkill. Instead, it is much faster if you just restart the
application pool that hosts the SharePoint web application containing your web part and then manually attach to the
process hosting your web part. You can restart the application pool via iisapp.vbs (located in the [drive letter]:\windows\
system32 folder) using the following command:
iisapp.vbs /a “[application pool name]” /r
You can make attaching to this process even easier by installing the Debugger feature for SharePoint, created
by Jonathan Dibble. This feature adds a new menu item to the Site Actions menu of a SharePoint site and is
described in detail in the blog post “Debugger ‘Feature’ for SharePoint ” at http://blogs.msdn.com/
sharepoint/archive/2007/04/10/debugger-feature-for-sharepoint.aspx. The feature can be
downloaded from the SharePoint 2007 Features site at CodePlex (http://www.codeplex.com/features/
Release/ProjectReleases.aspx?ReleaseId=2502). This list of free SharePoint features is maintained by
Scot Hillier.

Mots clés Technorati : MOSS 2007,WSS 3.0,Web Parts,IIS,VS 2005

12:32 AM | Add a comment | Send a message | Permalink | View trackbacks (0)

June 12

[MOSS 2007]Afficher des messages d'erreur explicites

Au cours de la mise en place de l' authentification par formulaire "Forms Authentication" comme publié sur le blog de Gael Duhamel,j'ai eu un petit soucis sur mon Appli dont je ne connais pas la source exactement,et après une longue discussion avec Gael il m'a proposer une astuce qui m'a permet de bien identifier mon problème,et que je veux partager avec vous afin d'afficher des messages explicites sur vos erreurs au lieu d' avoir une description standard de ce type:

Unknown Error
Troubleshoot issues with Windows SharePoint Services.

donc vous n'avez qu'a modifier le Web.config de votre application sharepoint située dans

Lecteur Local:\Inetpub\wwwroot\wss\VirtualDirectories\[repertoire du site] (par exemple 84) ,chercher l'entrée "CallStack" et modifier son statut a "true" pour afficher la pile des erreurs:

En suite vous devez modifier l'entrée "CustomErrors" pour afficher les messages d'erreurs:

Mots clés Technorati : WSS,MOSS,SharePoint

2:51 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

[MOSS 2007]Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports.

Pour voir l'etat d'usage de votre site "Site Usage Reports",vous devez activer cette option dans votre environnement sharepoint en procedant par les etapes suivantes:

1-dans la barre a gauche du site d'administration sharepoint,sous "Shared Services Administration" cliquez sur votre SSP.

2-sur cet ecran et dans la rubrique "Office SharePoint Usage Reporting",cliiquez sur "Usage reporting"

3-En suite sur la page "Configure Advanced Usage Analysis Processing" cochez les 2 checkboxe comme le montre l'image ci-dessous:

comme ca vous pouvez acceder aux statistiques d'usage de votre :

2:50 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

Adding Permission Levels

To create your own combination of permissions to meet specific site management needs, you can
create your own permission level sets as follows:
1. Navigate to a site having unique permission where you are the administrator.
2. From the site’s home page, click the Site Settings option from the Site Actions menu.

3. On the Site Settings page, in the Users and Permissions section, click the Advanced Permissions
link.

4. On the Permissions page, click the Settings link to view the Settings menu.
5. Select the Permission Levels option from the Settings menu.

6. If the current site is not the top-most site, a link will be available under See Also in the left
navigation area called Manage Permission Levels on Parent Web Site. Click this link.
7. On the Permission Levels page, click the Add a Permission Level link.

8. On the Add a Permission Level page, enter the following:
a. In the Name and Description section, enter the name for the new permission level. You
can also enter an optional description. The description is presented next to the name
when the permission level is listed for selection.
b. In the Permissions section, check the check boxes in front of all permissions that the
permission level should include.

NB:In my new permission level i selected all permissions.

c. Once all of the necessary information has been entered, click the Create button.
The new permission level is created, and you are returned to the Permission Levels page.

2:47 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

Web Part permettant d'uploader un fichier dans son liste des documents partagés

durant mes premiers pas sur sharepoint j'ai realisé un bout de code simple et intuitif qui me permet d'uploader un fichier dans ma liste des Documents Partagés:

sing System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;
using System.Collections;
using Microsoft.SharePoint.Administration;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;

using System.Net;
using System.Net.Mail;

namespace SharePoint.AspNetExample
{
    [Guid("57edfdc6-361a-4813-a7f2-1e261c5ad48b")]
    public class NormalPart : System.Web.UI.WebControls.WebParts.WebPart
    {

        //le control d'uploade
        FileUpload _objFileUpload = new FileUpload();

        protected override void CreateChildControls()
        {
            Controls.Add(_objFileUpload);

            Button btnUpload = new Button();
            btnUpload.Text = "Save File";
            this.Load += new System.EventHandler(btnUpload_Click);
            LiteralControl space = new LiteralControl(" ");
            Controls.Add(space);
            Controls.Add(btnUpload);
            LiteralControl backSpace = new LiteralControl("<br>");
            Controls.Add(backSpace);
        }

private void btnUpload_Click(object sender, EventArgs e)
{

            this.SiteCollectionUrl = "url de votre site sharepoint";
            using (SPSite objSite = new SPSite(SiteCollectionUrl))
            {
                using (SPWeb objWeb = objSite.OpenWeb())

                  {
                    SPList objList=null;
                    foreach(SPList item in objWeb.Lists)
                    {
                        if (item.Title.Equals("Shared Documents"))//pour recuperer votre liste de documents partagés et faire attention si vous utiliser une version "francais"

                       // de MOSS 2007 le nom sera "Documents partagés"
                        objList=item;
                    }
                    //SPList objList = objWeb.Lists["Documents partagés"];//ListName];
                    if (_objFileUpload.HasFile)
                    {
                        objList.RootFolder.Files.Add(_objFileUpload.FileName,_objFileUpload.PostedFile.InputStream, true);
                    }
                }
            }

        }

   private string _strSiteCollectionUrl;
        [Personalizable(PersonalizationScope.Shared), WebBrowsable(true), WebDisplayName("Site Collection URL"), WebDescription("Enter the URL of the site collection that contains the list a document is uploaded to")]
        public string SiteCollectionUrl
        {
            get { return _strSiteCollectionUrl; }
            set { _strSiteCollectionUrl = value; }
        }

}
}

maintenant ne vous faut que configurer votre projet et deployer votre web part dans le GAC.

N.B:sur cet article j'ai pas entamé la methode comment parametrer le projet sharepoint et deploiment.

2:45 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

View more entries