Second of all, this smells like Microsoft’s vendor lock-in strategy to me. Require people to buy 64 bit version of server and sql 2008 because now they need it for SharePoint! It’s an underhanded tactic from le Microsoft again!

Seriously, I’m going to become an Open source developer. This shit is just too much.

There are a lot of Sharepoint fanatics out there, but there are going to be a lot more business opportunities lost because of all the costs attached to this upgrade.

I’m a Sharepoint architect and I can assure you that we are going to lose more businesses and leads with this than ever before. Companies are not willing to spend all that huge amount of money in order to keep up to date with a tool that sometimes is not business critical. And what is business critical, the 2007 version is already able to provide it.

“heaps more support for the developer.”

To me it has always seemed like SharePoint workflows were programmed as an internal tool for the MS SharePoint team to make some “shiny” nice approval workflows, and a plethora of “Hello World” Visual Studio workflow designer presentations.

All my experience with SharePoint has been: Try it the most obvious way in the object model (SPListItem.MoveTo), when that doesn’t work, try changing the parameters of the methods, run with elevated privileges etc etc. Fish around for alternate solutions in the OM. Solution: a complete dumb workaround (recreate the item from scratch, iterating through versions and copying all attachments one by one then delete the original – oh and also set up roles and users.).

And workflows the same: “Oh cool you can put State Machine Workflow StateActivites inside each other! That’s just what my workflow needs! Now I’ll put an OnWorkflowItemChanged on the outer one. Yey! Oh. It doesn’t work. Back to the drawing board.”

And now I’m working on a two-workflow 38-state business process implemented as SharePoint Workflow.. HELP!

Once I install SQL Server 2008 Enterprise edition, all I will need is SharePoint 2010 to install inside of that VM.

I may also take a crack at the Windows 7 development capabilities to see what restrictions, if any, that placed on me as a developer. I can handle reasonable restrictions on total size, number of site collections, total rows in a list; but if it goes much beyond that, I’m headed back to the virtual machine environment for “real” MSS 2010 development.

It turns out my 2-year old Dell D820 laptop is 64-bit capable and has hardware virtualization available (just needed to turn it one in the BIOS) to help boost the performance of the VM I built. As a bonus, VMware 7 gives me virtual printer support for my VM’s.

Dave

Kind regards,
C. Marius