For more informations, visit Windows SharePoint Services 3.0 ,  Office SharePoint Server.

The above error will be thrown at the time of updating Library or Lists items due to authentication problem, or We didn’t have the rights to update the items.
By using the follwoing code, We can overcome this issue,

Web.AllowUnsafeUpdates = true;
item["Title"]=”Sample”;
item.Update();

or we can also use the follwoing code to overcome the above error, this will affect the WebApplication. This will change the Security settings of a Web Application to allow the anonymous user to update item.

web.Site.WebApplication.FormDigestSettings.Enabled = false;
item["Title"]=”Sample”;
item.Update();
web.Site.WebApplication.FormDigestSettings.Enabled = true;

or we can change the settings in Central Administration to anonymously update the items. But this method will be dangerous.

• Central Administration > Application Management > Web Application General Settings
• Choose the WebApplication to overwrite the settings
• Select the option Off in Web Page Security Validation as follows,

 This was the error, i recieved recently when i open an Excel sheet in browser.  I didn’t recived this error before, so i searched in recent log file. That file list out the following line

03/04/2009 14:27:33.07    w3wp.exe (0×14C4)    0×020C     Excel Services      Excel Services Web Front End  5pad    Critical     No Excel Calculation Services is available in the farm.[User: SHAREPOINT\system]

Then i understood, there is no Excel Calculation Services available in my Server Farm. So, I moved to my Central Administration Page,

• Central Administration -> Operations -> Services on Server 
  
•  Select Excel Calculation server role radio button
  
• Start the Excel Calaculation Services

Now I moved back to my Excel sheets Library and clicked the Excel File. Now all works fine for me…

Though, the syntax for that method is,

//Copy WebService Settings
string webUrl = “http://localhost:1000″;
WSCopy.Copy copyService = new WSCopy.Copy();
copyService.Url = webUrl+”/_vti_bin/copy.asmx”;
copyService.Credentials = System.Net.CredentialCache.DefaultCredentials;

//Declare and initiates the Copy WebService members for uploading
string sourceUrl = “C:\\Sample.doc”;
string[] destinationUrl = { “http://localhost:1000/Shared Documents/Sample.doc” };
WSCopy.CopyResult cResult1 = new WSCopy.CopyResult();
WSCopy.CopyResult cResult2 = new WSCopy.CopyResult();
WSCopy.CopyResult[] cResultArray = { cResult1, cResult2 };
WSCopy.FieldInformation fFiledInfo = new WSCopy.FieldInformation();
fFiledInfo.DisplayName = “Description”;
fFiledInfo.Type = WSCopy.FieldType.Text;
fFiledInfo.Value = “Sample Description”;
WSCopy.FieldInformation[] fFiledInfoArray = { fFiledInfo };

//Reading the document contents in to stream
FileStream strm = new FileStream(sourceUrl, FileMode.Open, FileAccess.Read);
byte[] fileContents = new Byte[strm.Length];
byte[] r = new Byte[strm.Length];
int ia = strm.Read(fileContents, 0, Convert.ToInt32(strm.Length));
strm.Close();

//Copy the document from SourceUrl to destinationUrl with metadatas
uint copyresult = copyService.CopyIntoItems(sourceUrl, destinationUrl, fFiledInfoArray, fileContents, out cResultArray);

This Copy Web service plays the role of copying, and moving documents with the field information’s. There are three classes to play this role,

Copy :
Provides methods for copying files between SharePoint sites or within a SharePoint site.
CopyResult  :
Represents the result of a copy operation.
FiledInformation :
Provides properties that define a field associated with a document copied by using a Copy web service operation.

The three methods within Copy class do the job for us to move the files in Sharepoint libraries,

GetItem  :
Generates a Byte array representation of a document that can be passed to the CopyIntoItems method to copy the document to a different server.
CopyIntoItems :
Copies a document represented by a Byte array to one or more locations on a server.
CopyIntoItemLocal  :
Copies a document from one location on a server running Windows SharePoint Services to another location on the same server.

By using this methods we can upload, download from different servers, local machines. In my coming posts I’ll explain each method in deep.

The Downloads for VS extensions for WSS Tools
VS 2008:
VseWSS12

VS 2005:
VseWSSv11

Version 1.2 of the Visual Studio 2008 Extensions for Windows SharePoint Services contains the following tools to aid developers in building SharePoint applications:

Visual Studio 2008 Project Templates
Web Part
Team Site Definition
Blank Site Definition
List Definition
Empty SharePoint Project

Visual Studio 2008 Item Templates (items that can be added into an existing project)
Web Part
Custom Field
List Definition (with optional Event Receiver)
Content Type (with optional Event Receiver
Module
List Instance
List Event Handler
Template

SharePoint Solution Generator
This stand-alone program generates a Site Definition project from an existing SharePoint site. The program enables developers to use the browser and Microsoft Office SharePoint Designer to customize the content of their sites before creating code by using Visual Studio.

I want to share with you all, about navigation features in both WSS3.0 and MOSS. SharePoint Navigation features called Navigation Providers are enabled in the root directory of webapplications’s web.config file to access widely. These named Navigation providers are added to the <SiteMap> element under <System.Web> Section.

Named Providers are defined under WSS3.0 are,

· SPNavigationProvider

· SPSiteMapProvider

· SPContentMapProvider

· SPXmlContentMapProvider

· SPXmlAdminContentMapProvider*

*This named procedure only available in Central Administration webapplication

All the above providers share the same namespace called Microsoft.SharePoint.Navigation

MOSS included some named providers in addition to the WSS3.0 named providers.

· AdministrationQuickLaunchProvider

· SharedServicesQuickLaunchProvider

· GlobalNavSiteMapProvider

· CombinedNavSiteMapProvider

· CurrentNavSiteMapProvider

· CurrentNavSiteMapProviderNoEncode

· MySiteMapProvider

· MySiteLeftNavProvider

· SiteDirectoryCategoryProvider

· UsagePagesSiteMapProvider

Provider Names:

AdministrationQuickLaunchProvider:

SharedServicesQuickLaunchProvider:

PortalSiteMapProvider:

*The each different value of NavigationType property in PortalSiteMapProvider object represents the following providers. There are Current, Global & Combined navigationtypes.

GlobalNavSiteMapProvider:

NavigationType: Global

Description: Include SPNavigationNodes from navigation in the TopNavigationBar collection of Windows SharePoint Services; respect global inheritance and include or hide settings.

CombinedNavSiteMapProvider:

NavigationType: Combined

Description: This is attached to the global navigation or top navigation menu by default.

CurrentNavSiteMapProvider:

NavigationType: Current

Description: Gets the PortalSiteMapProvider object that is attached by default to the current navigation or Quick Launch, respect to current inheritance settings and include or hide settings.

CurrentNavSiteMapProviderNoEncode:

NavigationType: Current

EncodeOutput: false

Description: Gets the PortalSiteMapProvider object that is attached to the breadcrumb navigation by default.

*Gets or sets whether to HTML-encode the Title property of each PortalSiteMapNode object.

MySiteMapProvider:

MySiteLeftNavProvider:

SiteDirectoryCategoryProvider:

UsagePagesSiteMapProvider:

SPNavigationProvider:

SPSiteMapProvider:

SPContentMapProvider:

SPXmlContentMapProvider:

SPXmlAdminContentMapProvider:

Available to only Central Administration application

soon I will come with a deep details about each navigation Providers.

Use System.Web.UI.WebControls.FileUpload control is named as fileUpload in code.

Sample code for uploading the file from Local Machine to ListItem attachments as follows,

//Check the FileUpload control has the file

if (fileUpload.PostedFile != null)

{item = list.Items.Add();

item["Title"] = fileUpload.FileName;

//Read the Contents from the file in Local machine

Stream fs = fileUpload.PostedFile.InputStream;                   

byte[] fileContents = new byte[fs.Length];

fs.Read(fileContents, 0, (int)fs.Length);

fs.Close();

// Add the file to the ListItem as an Attachment

SPAttachmentCollection attachments = item.Attachments;

string fileName = Path.GetFileName(fileUpload.PostedFile.FileName);

attachments.Add(fileName, fileContents); 

item.Update();                                           

}

 For that, we need to combine all required java script and Xaml files (used to display the Silverlight content) in to single assembly without any dependent files. It makes sense to embed the Xaml and java script file as a resource and reference it in programming using the WebResource.axd handler mechanism for extracting embedded resources.

I list out the following steps to add the Silverlight Content to SharePoint WebPart,

1.      Create a Webpart project and create or add the required java script and Xaml files to the project.

I used three files, are Silverlight.js, Scene.js and Scene.xaml

2.      Set the BuildAction property to “Embedded Resource” in properties window for each java script and Xaml.

This will use to include the files as Resources in an assembly.

3.      Add the assembly-level attribute System.Web.UI.WebResource to grant permission for these resources to be served by WebResource.axd and to associate MIME type for the response.

 [assembly: WebResource("Ktskumar.SLContent.Silverlight.js", "text/javascript" )]

[assembly: WebResource("Ktskumar.SLContent.Scene.js", "text/javascript")]

[assembly: WebResource("Ktskumar.SLContent.Scene.xaml", "text/xml")]

Ktskumar.SLContent represents the namespace, Now JavaScript and Xaml files are compiled into my assembly as embedded resources.

4.      Now, we can use the RegisterClientScriptresource() method of the Page.ClientScriptManagerclass to rendered the page with the referenced files.

 this.Page.ClientScript.RegisterClientScriptResource(GetType(), “Ktskumar.SLContent.Silverlight.js”);

this.Page.ClientScript.RegisterClientScriptResource(GetType(), “Ktskumar.SLContent.Scene.js”);</span

Include the above lines in the PreRender method to register the javascript files for the webpart.

5.      Add the following lines to the RenderWebPart method to host the <div> tag and call the Silverlight content to the webpart,

 string strLoad = “Silverlight.createDelegate(scene, scene.handleLoad)”;

output.WriteLine(“<div id=’” + this.ClientID + “‘ Style=”Width:500px;Height:200px”>”); 

output.WriteLine(“<script type=’text/javascript’>”);          

output.WriteLine(“if (!window.Silverlight)”);

output.WriteLine(“window.Silverlight = {};”);

output.WriteLine(“Silverlight.createDelegate = function(instance, method) {”);

output.WriteLine(“return function() {”);

output.WriteLine(“return method.apply(instance, arguments);”);

output.WriteLine(“}}”);

output.WriteLine(“var scene = new Scene();”); 

output.WriteLine(“Silverlight.createObjectEx({”); 

output.WriteLine(“source: ‘” + this.Page.ClientScript.GetWebResourceUrl(GetType(), “Ktskumar.SLContent.Scene.xaml”) + “‘,”); 

output.WriteLine(“parentElement: document.getElementById(’” + this.ClientID+“‘),”);

output.WriteLine(“id: ‘” + this.ClientID + “_ctrl’” + “,”);

output.WriteLine(“properties: {width:’100%’, height:’100%’, version:’1.0′ },”);

output.WriteLine(“events:{ onLoad: “+strLoad+“, onError: null  },”);

output.WriteLine(“context: null”);

output.WriteLine(“});”); 

output.WriteLine(“</script></div>”);

 Now you can install webpart to the SharePoint and see the Silverlight contents present in the SharePoint WebPart.

Coming soon, I will upload the source code for this webpart and more activities to come on Integrating the Silverlight with SharePoint. So always tuneup this blog.

Click here to download the source code for the above example.

This link contains 1 article and 6 samples which gives you the little idea about Infopath forms, Workflows and User access in BDC, AD using MOSS.