BNN National IQ Test 2009
Yesterday the BNN National IQ Test 2009 was on the Dutch television. I took the test and got a result of (IQ) 122 
Read more about: Intelligence Quotient
Office 14 Alpha Screenshots leak
Microsoft Office 14 ("Office 14" for short) is the working title for the next version of the Microsoft Office productivity suite for Microsoft Windows. It entered development during 2006 while Microsoft was finishing work on Microsoft Office 12, which was released as the 2007 Microsoft Office System. The major version number 13 has been skipped, presumably due to aversion to the number 13. It was previously thought that Office 14 would ship in the first half of 2009,[1] but more recent information suggests a late 2009/early 2010 release timeframe.Microsoft Office 14 is expected to be released around the time of Windows 7. According to an article published in InfoWorld in April 2006, Office 14 will be more "role-based" than previous versions. The article cites Simon Witts, corporate vice president for Microsoft's Enterprise and Partner Group, as claiming that there would be features tailored to employees in "roles such as research and development professionals, sales persons, and human resources." Borrowing from ideas termed "Web 2.0" when implemented on the Internet, it is likely that Microsoft will incorporate features of SharePoint Server in Office 14.
Office 14 will implement the ISO compliant version of Office Open XML which was standardized as ISO 29500 in March 2008. Microsoft plans to offer a Web-based version of its Office productivity suite, known as Office Web, that will debut with the release of Office 14. Office Web will include online versions of Word, Excel, PowerPoint and OneNote.
Original Text: http://en.wikipedia.org/wiki/Microsoft_Office_14
On January 15, 2009, screenshots of an Office 14 alpha build were leaked by a tester. You can see them here: http://www.neowin.net/news/main/09/01/15/office-14-alpha-screenshots-leak
WSS Extensions 1.3 for Visual Studio 2008 CTP
On the Microsoft SharePoint Team Blog you can read about the CTP release of version 1.3 of Windows Sharepoint Services 3.0 extenisions for Visual Studio 2008 (VSeWSS).
The new features in VSeWSS 1.3 are:
· Can be installed on x64 Server OS machines running SharePoint x64. Previously only x86 Server OS could be used.
· Separate build commands for package, deploy and retract are added
· Command line build, package and retract commands are included enabling continuous integration and build servers. Previously command line build of SharePoint projects was very difficult
· Refactoring support for renaming of Web Parts. Previously renaming a web part required changes in several files in the project
· WSP View improvements for consistency of deleting feature elements, merging features and adding event receivers to features
· Solution Generator can now generate solutions from publishing sites. Previously only regular sites could be generated
· Allowing partial trust BIN deployments of web parts. CAS configuration must still be provided by the developer.
· New project item template for SharePoint RootFiles items
· Deployment will now optionally remove conflicting existing features on the development server prior to redeployment. Previously any feature name conflicts would result in an error
· Ancillary assemblies such as for business logic can now be added to the SharePoint Solution WSP
· Hidden features related to Site Definition projects are now shown in WSP View. They are no longer hidden
· For advanced users a fast deploy is included to update only the compiled assembly on the SharePoint development installation
· The User Guide is now installed with the extensions instead of being a separate download
The final release of VSeWSS 1.3 is planned for the North American Spring of 2009.
Download now!
Site Milestone - More than 1000 visits a month
Today SharePointDevelopment.nl reaches the milestone of more than 1000 Site Visits a month 
CAML Query with dynamic date evaluation
You can use this caml for example in a calendar list.
<Where>
<Geq>
<FieldRef Name="EventDate" />
<Value Type="DateTime" IncludeTimeValue="TRUE">[My Date]</Value>
</Geq>
</Where>
// For [MyDate] you have to use: SPUtility.CreateISO8601DateTimeFromSystemDateTime(DateTime.Today)
// You have to convert the date from a DateTime value into a CAML Date format, which is the ISO8601 format.
// This works only for date, not time (even using the IncludeTimeValue attribute). [/code]
You can also use the next code to get item(s) that have an ImageCreateDate in the last seven days
<Query>
<Where>
<Geq>
<FieldRef Name="ImageCreateDate" />
<Value Type="DateTime">
<Today OffsetDays="-7" />
</Value>
</Geq>
</Where>
</Query>
[/code]
Quickly filter a List or Document Library View using URL
This is very useful when you're having a lot of items in a list or document library and you need a quick filter.
If you'll select the filter field it can happen that it will load for a long time. So lately I'm using URL. Suppose you have a long list of contacts and you need to find a contact named Boris.
In the AllItems.aspx - view of the page, add parameters
?FilterField1=[Field Name]&FilterValue1=[Value]
You can add more filterfield and filtervalue parameters to apply filters to more fields (FilterField2, FilterValue2, ...)
// For example you have a list (MyCalendar) containing a choice field "Activity". Choices could be either Private, Work or School
// A quick filter could be:
http://[site_URL]/lists/MyCalendar/AllItems.aspx?FilterField1=Activity&FilterValue1=Work
! Note ! Remember to use "%20" for a white space in field names: Field Name Nick Boumans become Nick%20Boumans
Remembering the Query String
You already used it but how dit you passed that value using a Query String?
"A query string is the part of a URL that contains data to be passed to web applications (e.g. http://server/path/program?query_string=value)."
// A) Add a querystring to the entire url
String newUrl = Context.Request.Url.ToString() + "?ItemID={0}";
// B) Check or there is a Query String
if(Page.Request.QueryString.AllKeys.Length == 0)
{ // Do something }
// C) Write all keys and values from the Query String
using System.Collections;
using System.Collections.Specialized;
...
NameValueCollection collection = Request.QueryString;
String[] keyArray = collection.AllKeys;
Response.Write("Keys:");
foreach (string key in keyArray) {
Response.Write(" " + key +": ");
String[] valuesArray = collection.GetValues(key);
foreach (string myvalue in valuesArray) {
Response.Write("\""+myvalue + "\" ");
}
}
[/code]
Excellent Article about Lotus Notes to Office 2007 trends and migrations
Redmond Channel Partner Online:
http://rcpmag.com/features/article.aspx?editorialsid=724 A little bit out of date but to the point.