Just seen this on the SharePoint Team Blog found here

• SharePoint Server 2010 will be 64-bit only.
• SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
• SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.

I wonder what this means for all those development houses out there who have to go and replace laptops, with new copies of Windows 2008, SharePoint 2010 and SQL Server.

$$$$$$$$$$!!!!!!!!!

I’ve recently installed the RC of Windows 7 on my home machine. One thing that’s different is Virtual PC 2007 doesn’t work anymore on Windows 7. Instead you have the new ‘Virtual PC’ application that can be downloaded as an add-on from Microsoft.

This provides the much-talked about XP mode that permits users to run Windows XP applications from within Windows 7. But what about existing VM’s?

Well I was able to load up an existing VM I had and everything seemed to work ok. The interface is kinda different in that you can’t use ALT+DELETE to send the CTRL+ALT+DELETE combination. Instead there’s a menu item that sends it instead.

Additionally, you can install the integration components. This permits the VM to access things such as drives, clipboards etc from the host OS. The only issue is that when you try to run the VM again in Virtual PC 2007 the whole thing crashes and burns. It’s probably the integration components that’s causing it as it seems to be the only thing that’s changed between versions. Be warned!

[UPDATE]

Yep it’s definitely the integration components. I was able to boot the VM and access debug mode. From there I uninstalled the integration components and voila, the VM worked again under Virtual PC 2007 SP1.

Here’s a wee link I discovered on Andrew Woodward (MVP’s) blog. Its a free webinar on SharePoint and SQL Server 2008 Reporting Services.

Here’s the blurb from the site:

Put the Pedal to the Metal
Reporting through SharePoint – Webinar

Date:    Thursday, May 7th

Time:    2 to 3 pm Eastern (1 to 2 pm Central)

There is no charge for this webinar

SharePoint guru Coskun "Cujo" Cavusoglu will be your driver and discuss how Microsoft SQL Server 2008 Reporting Services has two gears: Native and SharePoint Integrated. Native mode is like driving on a highway (smooth and fast) but there is a speed limit. Incorporating Reporting Services into MOSS via SharePoint Integrated mode enables users to put the pedal to the metal and speed through tasks.

We will explore how the integration works and how to get the most out of your investment if you set up Reporting Services in SharePoint Integrated mode. You will learn the functionalities that didn’t make it to the integrated mode, or unsupported scenarios, that you should be fully aware of before putting the foot to the floor. Both pros and cons will be discussed.

Recently I was tasked with writing an event-handler that basically increments a unique number and assigns this to the ‘Document Number’ list item in a document library once a document is added.

Sounds reasonable yes? Usually it is simply a case of adding code to the itemAdded / ItemAdding or ItemUpdate / ItemUpdating events of the list, getting a new number and assigning it to the ‘document number’ column in the list.

The problem is when Check in & Checkout is enabled on the document library. When this is enabled, a lot of strange and wonderful things happen, specifically in regard to how the events fire. I’ve basically debugged the sequence and it’s shown below:

Standard Document Library, no Check In or Check Out turned on.

New document from the ‘New’ menu item

• ItemAdding
• ItemAdded

Saving document using the same name as an existing document

• ItemUpdating
• ItemUpdated

Uploading a new document using the ‘upload’ menu item

• ItemUpdating
• ItemUpdated
• (Prompted user for document properties)
• ItemUpdating
• ItemUpdated

Multiple uploads. 1 new document, 1 existing. NB, No Doc Properties window is shown during the upload.

• ItemUpdating
• ItemUpdated
• ItemAdding
• ItemAdded

Multiple uploads, 2 existing documents in the document library

• ItemUpdating
• ItemUpdating
• ItemUpdated
• ItemUpdated

Now lets turn on Check In and Check Out on the document library.

Check In turned on. New document

• ItemAdding
• ItemAdded
• ItemCheckingOut
• ItemCheckedOut
• At this point your prompted to check in.
• ItemUpdating
• ItemUpdated
• ItemUpdating
• ItemCheckingIn
• ItemUpdated
• ItemCheckedIn

New document, Check In turned on, but user didn’t check in the document.

• ItemAdding
• ItemAdded
• ItemCheckingOut
• ItemCheckedOut

User proceeds to check in the document that was added in the previous step.

• ItemUpdating
• ItemUpdated
• ItemUpdating
• ItemCheckingIn
• ItemUpdated
• ItemCheckedIn

Upload single document

• ItemAdding
• ItemAdded
• Prompted for doc properties!
• ItemUpdating
• ItemUpdating
• ItemUpdated
• ItemCheckingIn
• ItemUpdated

2 new documents uploaded

• ItemAdding
• ItemAdding
• ItemAdded
• ItemAdded

2 documents uploaded in previous step. Need checked in. Events fire once per document.

• ItemUpdating
• ItemCheckingIn
• ItemUpdated
• ItemCheckedIn

1 document dragged in from Explorer View

• ItemAdding
• ItemAdded

Multiple documents dragged in from Explorer View

• ItemAdding – doc1
• ItemAdded
• ItemAdding – doc2
• ItemAdded

Checking in Explorer Documents from previous step (runs per document)

• ItemUpdating
• ItemCheckingIn
• ItemUpdated
• ItemCheckedIn

So what’s the bottom line? Ultimately the event handler should be tailored to determine if Check In/Checkout is enabled. If Check In/ Check Out isn’t enabled, use Adding/Added/Updating/Updated. If it is, use the Checked In handler. I haven’t come across a technique to determine through the properties item if check in is turned on. I suspect I’d have to access the list and go from there.