Comments for Fred Morrison's Weblog

Comment on Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) by fredmorrison

fredmorrison — Mon, 02 Nov 2009 19:00:56 +0000

Now that VMware Workstation 7.0 and VMware Player 3.0 are out of beta and are generally available, I’ve built a new 64-bit Windows Server 2008 R2 Enterprise virtual machine under the small Windows 7 Ultimate partition on my existing laptop.

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.

Comment on 64-bit only requirement will dampen SharePoint 2010 uptake by Dave

Dave — Mon, 02 Nov 2009 15:05:56 +0000

Wow,
If anyone can create a 64 bit hardware emulator that will run on a 32 bit machine, that would be incredible! (If not nye impossible…)

Dave

Comment on Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) by C. Marius

C. Marius — Fri, 30 Oct 2009 16:16:11 +0000

Well maybe you’re right or maybe not…but it still possible to build a developer machine based on “workstation”, such as Windows 7 RTM x64…which works just fine (many others have written about it…see mine at http://nettitude.spaces.live.com/)! And better yet..try enabling the “SharePoint 2010 Developer Dashboard”…that gives more ideas!
There are some tweaks…but i guess that as long as the comunity exists…there will always be ways.

Kind regards,
C. Marius

Comment on WSS/MOSS 2007 Service Pack 2 breaks People Picker by fredmorrison

fredmorrison — Tue, 27 Oct 2009 14:53:26 +0000

There is a KB article or official Microsoft SharePoint Team Blog on the solution, but I don’t have a lot of time at the moment to remember where to find it. If I ever get a chance to look again, I’ll post it here, but to be honest, that may be months from now based on my current workload.

Comment on WSS/MOSS 2007 Service Pack 2 breaks People Picker by al

al — Tue, 27 Oct 2009 11:10:38 +0000

I have this problem now. Can you help me and public detail decision ?

Comment on Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) by fredmorrison

fredmorrison — Tue, 20 Oct 2009 15:45:14 +0000

This is a change from the June 2009 set of requirements. I’m going to view some of the videos to see what restrictions, if any, there are on developing an MSS 2010 workflow under 64-bit Windows 7 or 64-bit Vista.

Comment on Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) by Gil

Gil — Tue, 20 Oct 2009 15:36:53 +0000

You can run SharePoint 2010 on Windows 7!

Comment on 64-bit only requirement will dampen SharePoint 2010 uptake by Srikant

Srikant — Sun, 11 Oct 2009 08:20:56 +0000

I agree with ‘fredmorrison’ completely. Microsoft should have provided some way out thinking about we developers who cannot go for new hardware/software so easily.

They should provide a 64 bit VPC which we can run on our 32 bit machines.

Comment on WSS/MOSS 2007 Service Pack 2 breaks People Picker by Barno

Barno — Fri, 02 Oct 2009 11:02:57 +0000

We had this problem after applying SP2 on our MOSS 2007 server. We followed the steps from George Khalil’s post on this URL:

http://www.gk.id.au/2009/04/people-picker-sharepoint-and-forest.html

This fixed our broken people picker.

Thanks to George!!!

Comment on MSDN Workflow Stuff by fredmorrison

fredmorrison — Sat, 26 Sep 2009 10:38:27 +0000

While I have not tried the specific scenario you describe, from what I know about a Replicator, once the Replicator’s Initialized event has completed, you cannot dynamically add more items to the ChildData list. Also, your ChildData list should be a serializable list that is global to the workflow when it starts. Don’t wait until the workflow modification kicks in to make a new list.