If you ever wanted to know why is office 2007 so much better than 2003 with SharePoint 2007?

this document will explain it all:

Microsoft Windows SharePoint Services 3.0 and Office SharePoint Server 2007 provide advanced collaboration and enterprise content management capabilities for end users through rich, contextual integration with Office Professional Plus 2007 and Office Enterprise 2007. These latest versions of their respective platforms were developed together for maximum integration, with the expressed purpose of enabling the most powerful user experience possible. While the 2007 Office Suites and Windows SharePoint Services 3.0 and Office SharePoint Server 2007 provide much new and improved functionality compared to their previous versions, the combined deployment of the latest client programs and server technologies is necessary to achieve the best Office and SharePoint integration features.
By leveraging the best Office and SharePoint integration features, you will be able to collaborate more productively, manage your enterprise’s information content and people driven processes more effectively, and improve your business insight more rapidly.

Download:
Microsoft® Office Programs and SharePoint® Products and Technologies Integration

Today my new webpart is almost finished...

I'm proud to present a RIA webpart that enables SharePoint admins to provide a more graphical menu for the sharepoint navigation. It is implemented within a feature that enables you to add the webpart to your page from the webpart list.





When the webpart is added to your page the left navigation is instantly mirrored on the bottom of your page. Currently the webpart does not remove the left navigation.


I need to check before I can publish the webpart. Any comments are welcome.

Darren Johnstone created an interesting JavaScript API for SharePoint.

The following examples illustrate the use of the JavaScript API for SharePoint and Office Live. These examples are intended to demonstrate the core uses of the API for solution developers.
* Get the full definition of a list
* Get the full definition of a list and associated view
* Get the basic detail of all lists in a site
* Get the GUID of a list from it’s name
* Querying a list using the Lists web service
* Querying a list using the List Data Retrieval Service
* Create a new list from an existing list template
* Delete a list
* Create one or more new list items
* Update one or more list items
* Delete one or more list items
* Create a new folder within a list
* Performing a keyword search
* Performing a full text search


The API contains 23 JavaScript files.

Let me show you how easy we can create a call to Lists.asmx web service and retrieve all the items:

var lists = new SPAPI_Lists('http://mossserver')
var items = lists.getListItems('Tasks');
if (items.status == 200)
{
var rows = items.responseXML.getElementsByTagName('z:row');
//START DOING JS MAGIC
}

If you're developing custom web parts and you're favorite web part is the content editor web part. Go check out this library.

More information can be found at the related link section of this post.

the SPSite class and SPWeb class objects, are created as managed objects. However, these objects use unmanaged code and memory to perform the majority of their work.
The managed part of the object is small; the unmanaged part of the object is much larger.
Because the smaller managed part of the object does not put memory pressure on the garbage collector, the garbage collector does not release the object from memory in a timely manner.
The object's use of a large amount of unmanaged memory can cause some of the unusual behaviors described earlier.
Calling applications that work with IDisposable objects in Windows SharePoint Services must dispose of the objects when the applications finish using them. You should not rely on the garbage collector to release them from memory automatically

Best practice:

Dispose method
using clause
try, catch, and finally blocks

More information can be found at the SharePoint Best Practice Site

Microsoft SharePoint Team announced yesterday that
Microsoft wants to help developers build better quality code that manages available memory better. We are now building a console tool that will help to evaluate customer code against the guidance that is provided. The tool, called SPDisposeCheck, will open your custom compiled assemblies recursively and validate them against the Microsoft published guidance. The output from the tool will contain messages that may indicate the SPSite and SPWeb Dispose() methods guidance are not being followed in the customers source code. While these messages need expert evaluation in order to determine if the software is not performing properly, in some cases just running the tool on your custom code can lead you to simple fixes that improve the quality and performance of custom code on SharePoint.

This tool is planned for release during the coming North American Winter.
More information can be found at the Microsoft SharePoint Team Blog

This is a guide for setting up an InfoPath form that will fill in other textboxes with data retrieved from a SharePoint list or library, this form will be published to a SharePoint form library in order to provide end users an easy way to fill in a form.

This solution is created by using InfoPath 2007 and MOSS 2007. This is a document created in order to help other SharePoint developers while they are creating InfoPath forms that need the same functionality.

CONTENT

1 Introduction
2 Auto Fill in Infopath formulier with ID from sharepoint list
3 Add a data connection that points to your SharePoint list
4 Add a rule to fill in the other controls
5 Finished

klik here to open the document