A quickly and simple solution that i found to do it is the SPSilverlight web part, a web part that allows you to add a Silverlight control to SharePoint.

The only configuration that you need to known is the path where the XAP file is stored in SharePoint (on the layout’s folder, on the library…).

To use this web part you need to install the following package:

http://spilverlight.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35120

The post Add Silverlight control to SharePoint appeared first on Blog IT.

Basically, the BDC is a new MOSS’s feature that allows you to integrate business data from the business applications, without spending much effort and without writing any line of code.

The interesting BDC videos to how to start to work with this feature are the following:

• Create and Configure a Business Data Catalog

• Use the Business Data Catalog

Firstly, I watched “Use the Business Data Catalog” video and i was scared because to use this SharePoint feature i need to import an application definition file. And, how do i create it? Actually i don’t want to implement it manually, and after searching about this file’s generation, i found the first video’s topic that explains how to generate this file. So if you want to generate Application Definition file you can use the Application Definition Editor that is inside of the SharePoint Server 2007 SDK.

Well, for me the important question after watched this videos is: When do i should use BDC? For example, you should use BDC when your client has a LOB application and SharePoint Portal, he wants to integrate this application but he don’t want to spend much effort with this integration, because he spent much effort with the individual application’s maintenance. I think that isn’t a good approach for all the business use cases, but it’s a good approach for the simple integrations between applications.

The post Bussiness Data Catalog on SharePoint appeared first on Blog IT.

Today i will talk about Silverlight and Sharepoint 2007 integration. The problem with this integration is if i have a webpart that contains a Silverlight control, my webpart doesn’t appear. And then, How do you use Silverlight controls in the SharePoint site?

You have to ensure that your server environment is configured for SharePoint and Silverlight intregation. To do this, you should do the following:

1. Put the XAP files into the Sharepoint Site Bin Folder.
2. Change the MIME type in the IIS (Internet Information Services).
3. Change the web.config file in your root SharePoint Site.
4. Ensure that the System.Web.Silverlight dll is in your GAC (Global assembly cache).

Put the XAP files into the Sharepoint Site Bin Folder

You must have to put your XAP files into the Bin Folder, but exist other ways to deploy the that i will talk in the next post.

Steps:

• Add ClientBin Folder that contains XAP files in the Bin Folder.

Changing the MIME Type

You should add MIME support for Silverlight applications that you build and deploy to your SharePoint server.

Steps:

• Click Start, Administrative Tools, and then select Internet Information Services (IIS) Manager.
• Under Web Sites in the IIS, click on the web application that represents your SharePoint site.
• Click “MIME Types”, and then click “Open Feature”.
• In the Mime Type View, click Add, add the file-type extension
  • type .xap as the “File name extension”
  • application/x-silverlight-2 (for Silverlight 2.0) or application/x-silverlight-app (for Silverlight 3.0) as the “MIME Type”.
• Click OK to add the new MIME type to IIS.

Editing the web.config File

By default, the web.config file of your SharePoint Site does not support Silverlight applications.

This is the most hardest Configuration’s step, because it is required to copy some configurations to the web.config file. To simplify that, i found a tool named stsadm.config in the CodePlex, that it will add all of the Silverlight configurations needed to the web.config of the Sharepoint Site.

Steps:

• Deploy stsadm.config’s solution writing deploy.stsadmwebconfig.cmd in the command prompt.
• You must use the following Xml configuration file

    1: <ConfigEntries owner="Administrator">
  
  
  
    2: <ConfigEntry>
  
  
  
    3: <Name>add[@verb='GET,HEAD'][@path='ScriptResource.axd'][@validate='false'][@type='System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35']</Name>
  
  
  
    4: <Path>configuration/system.web/httpHandlers</Path>
  
  
  
    5: <Value><![CDATA[<add verb='GET,HEAD' path='ScriptResource.axd' validate='false' type='System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>]]></Value>
  
  
  
    6: <ModType>EnsureChildNode</ModType>
  
  
  
    7: </ConfigEntry>
  
  
  
    8: <ConfigEntry>
  
  
  
    9: <Name>add[@name='ScriptModule'][@type='System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35']</Name>
  
  
  
   10: <Path>configuration/system.web/httpModules</Path>
  
  
  
   11: <Value><![CDATA[<add name='ScriptModule' type='System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'/>]]></Value>
  
  
  
   12: <ModType>EnsureChildNode</ModType>
  
  
  
   13: </ConfigEntry>
  
  
  
   14: <ConfigEntry>
  
  
  
   15: <Name>SafeControl[@Assembly='System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35'][@Namespace='System.Web.UI'][@TypeName='*'][@Safe='True']</Name>
  
  
  
   16: <Path>configuration/SharePoint/SafeControls</Path>
  
  
  
   17: <Value><![CDATA[<SafeControl Assembly='System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35' Namespace='System.Web.UI' TypeName='*' Safe='True' />]]></Value>
  
  
  
   18: <ModType>EnsureChildNode</ModType>
  
  
  
   19: </ConfigEntry>
  
  
  
   20: <ConfigEntry>
  
  
  
   21: <Name>SafeControl[@Assembly='System.Web.Silverlight, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'][@Namespace='System.Web.UI.SilverlightControls'][@TypeName='*'][@Safe='True'][@AllowRemoteDesigner='True']</Name>
  
  
  
   22: <Path>configuration/SharePoint/SafeControls</Path>
  
  
  
   23: <Value><![CDATA[<SafeControl Assembly="System.Web.Silverlight, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" Namespace="System.Web.UI.SilverlightControls" TypeName="*" Safe="True" AllowRemoteDesigner="True" />]]></Value>
  
  
  
   24: <ModType>EnsureChildNode</ModType>
  
  
  
   25: </ConfigEntry>
  
  
  
   26: </ConfigEntries>
  

• Copy the previous xml file to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\CONFIG.
• Run the following command in the command prompt (replace the SharePoint Site Url):

stsadm -o webconfig_apply -url http://createsrv:5003 -configfile SilverlightInSharepoint.xml

Add System.Web.Silverlight dll to GAC

This step does make sense for Silverlight 2.0 because the controls in the System.Web.Silverlight assembly were officially deprecated for Silverlight 3.0. If you are using Silverlight 3.0, you don’t need to add System.Web.Silverlight.dll to GAC.

Otherwise, if you are using Silverlight 2.0, you must need to add the assembly to the GAC. This assembly resides in the following path: C:\Program Files\Microsoft SDKs\Silverlight\v2.0\Libraries\Server.

Finally, your Silverlight control just appears in the Sharepoint.

The post Using Silverlight in Sharepoint 2007 – Configuration appeared first on Blog IT.

SharePoint in Plain English

The post SharePoint in plain English appeared first on Blog IT.

When you change SharePoint Diagnostic Logging to use verbose, the log files will growth rapidly, so you should only use verbose mode for short periods of time.

If you change a lot of the default settings, since each category is set to a specific level (let’s say, for Backup category levels “Error” and “medium”, while maybe Search was at “Information” and “Verbose”) and want to restore everything backup to default the best way is using the STSADM command STSADM.EXE -o setlogginglevel -default

But if you have enough patience and you know exactly the levels for all categories, you can of course do it using the UI 😉

The post Change SharePoint Diagnostic Logging appeared first on Blog IT.

The post Get SharePoint List in XML Format appeared first on Blog IT.

http://office.microsoft.com/en-us/sharepointdesigner/default.aspx

The post SharePoint Designer will be free appeared first on Blog IT.

 Here how to set it up http://www.sharepointblogs.com/teameli/archive/2009/02/20/using-spdisposecheck-in-visual-studio.aspx

The post Using SPDisposeCheck in Visual Studio 2005/2008 appeared first on Blog IT.

Ontem juntamente com o meu colega e amigo André Vala fiz uma sessão (WUX207) sobre Deployment em SharePoint, estiveram cerca de 80 pessoas na sala, gostei da forma como a sessão decorreu, contudo tivemos que baixar o nível da sessão visto estar preparada para um nível mais perto do 300.

A ideia principal da sessão era mostrar as formas de fazer deployment em SharePoint e principalmente a razão para se usar ao máximo, quando possível, solutions e features.

Aproveito para disponibilizar o conteúdo da apresentação, PDF e demos.

Para quem viu a apresentação espero que tenha gostado, caso tenham alguma dúvida estão à vontade para as colocar através do link "Email" que se encontra no menu do blog.

Para além da sessão acima referida, a |create|it| este presente com mais dois speakers, João Pedro Martins que fez três sessões e Marco Silva que fez uma sessão sobre Serviços REST sobre WCF.

The post DevDays 2009 @ IST – TagusPark appeared first on Blog IT.

One of the most exciting features included in SharePoint 2007 is workflow support and the possibility of developing our own custom workflows (for more information about workflow development in the SharePoint 2007 platform please click here).

While it is possible to develop workflows to automate a series of activities without any human intervention, the full power of workflows in the SharePoint platform can only be achieved with human-oriented workflows. These workflows are characterized by creating and assigning tasks to users that must complete them in order to fulfill the purpose of the workflow. Some examples of out of the box human-oriented workflows that are included with MOSS 2007 are Approval, Collect Feedback and Issue Tracking.

In the SharePoint world, the most common usage of human-oriented workflows is in the context of document libraries, to perform some work when a new document is uploaded into a document library. Typically, in such scenario, tasks are created and assigned to users throughout the workflow lifetime that will complete them until the workflow purpose has been fulfilled. Having the workflow goal to be achieved is the desired and most common scenario, but unexpected actions may occur before the end of the workflow such as a user to delete the document. The following example will show you how to handle this situation in a custom workflow by using the OnWorkflowItemDeleted activity.

Example

The OnWorkflowItemDeleted activity can be used within a custom workflow to handle an item deletion in any SharePoint list. In this example, this activity will be used to delete all uncompleted tasks associated with the deleted item. After dragging and dropping the OnWorkflowItemDeleted activity into the workflow designer, the Invoke property must be set to the event handler that will perform the work.

For the purpose of this example, please consider the simple approval workflow in the following image:

In this workflow, a parallel activity with two branches is used. One contains the main workflow logic while the other contains a OnWorkflowItemDeleted activity that will handle the item deletion. The Invoke event property was set to be handled by an event handler method called OnWorkflowItemDeleted_Invoked. Let’s take a look at the code:

public sealed partial class ApprovalWorkflow : SequentialWorkflowActivity
{
    /// <summary>
    /// Handles the workflow item deleted event.
    /// </summary>
    /// <param name="sender"></param>
    /// <param name="e"></param>
    private void OnWorkflowItemDeleted_Invoked(object sender, ExternalDataEventArgs e)
    {
        //delete uncompleted tasks when 
        //an item is deleted
        SPWorkflow workflowInstance = 
            workflowProperties.Workflow;
        SPWorkflowTaskCollection taskCollection = 
            GetWorkflowTasks(workflowInstance);
        for (int i = taskCollection.Count; i > 0; i--)
        {
            SPWorkflowTask task = 
                taskCollection[i - 1];
            using (SPWeb web = 
                workflowProperties.Web)
            {
                if (task[SPBuiltInFieldId.TaskStatus]
                    .ToString() != SPResource.GetString
                    (new CultureInfo((int)web.Language, false),
                    "WorkflowTaskStatusComplete", new object[0]))
                {
                    task.Delete();
                }
            }
        }
    }

    /// <summary>
    /// Reads the workflow tasks. This method 
    /// is implemented because the Tasks property
    /// of the SPWorkflow instance takes a 
    /// while to be populated.
    /// </summary>
    public static SPWorkflowTaskCollection 
        GetWorkflowTasks(SPWorkflow workflowInstance)
    {
        SPWorkflowTaskCollection taskCollection = null;
        bool tasksPopulated = false;
        while (!tasksPopulated)
        {
            try
            {
                taskCollection = workflowInstance.Tasks;
                tasksPopulated = true;
            }
            catch { }
        }

        return taskCollection;
    }
}

In the previous example, the following actions are being performed:

• In the OnWorkflowItemDeleted_Invoked event handler, the workflow instance task collection is obtained by calling the GetWorkflowTasks method;
• The task collection is iterated and the each task status is checked to verify if it is still uncompleted;
• If so, the task is deleted.

The post SharePoint 2007 Workflow – Using the OnWorkflowItemDeleted activity appeared first on Blog IT.