Google within the office? The end of SharePoint Search?

Official Google Blog: 9,000 and counting

What implications would this have on SharePoint Search? One of the strong selling features of SharePoint IMHO is the indexing of all data within the company. We call it the "internal google". Having the actual Google indexing and search technology available within the company is surely a challenge to any search and indexing enterprise software.

What would you choose if you had a choice betweenbetween SharePoint Search and Google Search? Google within the office, that has quite a nice ring to it... And the price?
Google Search: Search business applications. Support for document-level security. Search up to 50,000 documents for just $1,995

SharePoint 2007: Programmatically add an item/event to a SharePoint 2007 calendar using .NET code

Useful when adding calendar or other events to SharePoint lists via the Lists web service.

http://enterprise-solutions.swits.net/infopath2007/article.php?t=programmatically-add-item-sharepoint-calendar-infopath&c=infopath2007
Things of note:

Lists Web Service
You can update items programatically using the Lists webservice: http://Server_Name/Site_Name/_vti_bin/Lists.asmx

Batch XML

<batch><method id="1" cmd="New"><field name="Title"><field name="Location"><field name="Description"><field name="EventDate"><field name="EndDate"><field name="fAllDayEvent"></method></batch>

Date Formats:
YYYY-MM-dd or YYYY-MM-ddTHH:mm:ssZ.

You can specify whether an event is an All Day Event by setting the value of the fAllDayEvent field to 1 and passing in dates that have the YYYY-MM-dd format.

Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions

Ok, maybe this blog was about using SharePoint Designer and avoiding coding, but in some cases you have to code. In that case as a developer you should try to make your life as simple as possible.

Back when I was developing webparts in 2003, deploying a webpart was a long(ish) procedure of signing assemblies and copying to the GAC and a lot of of other steps.

Fast forward to SPS 2007 and I've come to write my first webpart. Seems like the process has been made easier thanks to a nice Visual Studio 2005 extension: Windows SharePoint Services 3.0 Tools: Visual Studio 2005 Extensions. If you select the Web Part project, as soon as you build, your webpart is immediately deployed to your local SharePoint installation. Quite elegant I must say ... Haven't tried it and don't know if it works with remote servers or anything, but this is already a good step IMHO.