Comments for Fred Morrison's Weblog

Comment on Where is SharePoint 2010 Service Pack 1? The world wonders. by Dave

Dave — Thu, 10 Mar 2011 21:40:45 +0000

http://blogs.technet.com/b/office_sustained_engineering/archive/2011/02/09/1office-2010-and-sharepoint-2010-momentum-amp-service-pack-1-update.aspx

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by fredmorrison

fredmorrison — Mon, 20 Dec 2010 15:30:46 +0000

My understanding is that WF 4.0 was not “fully baked and ready to go” when SharePoint 2010 was being designed and coded; therefore, we’re stuck with WF 3.0 in SharePoint 2010 workflows designed using the SharePoint 2010 workflow templates included in Visual Studio 2010.

One of three things will probably happen:
1. The ability to create and run WF 4.0-based workflows in SharePoint 2010 with full “tooling support” (replacements for the SharePoint 2010 workflow templates in Visual Studio 2010) will be slipstreamed in via a Service Pack (probably not SharePoint 2010 SP1).
2. Somebody will come up with a crude, “feels like it’s bolted not, not built in” kludge to make it possible to create and debug SharePoint 2010 workflows based on WF 4.0. Keep your eyes on CodePlex and other open-source locations because waiting on Microsoft to act requires near-infinite patience.
3. We wait until the next version of SharePoint (2014?) and hope it at least supports WF 4.0 via the “tooling” (Visual Studio). Don’t hold your breath expecting the next version of SharePoint to fully support the next version of WF (4.5? 5.0?).

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by scott

scott — Mon, 20 Dec 2010 14:16:00 +0000

I’ve read over the improvements to 2010 workflows, and they still do not address the main horrendus shortfalls of sharepoint 2007 workflows.

- Inability to resume after a sharepoint restore, or data migration.
- If a workflow fails, you are unable to restart it at the last workflow step.

I don’t know why anyone would use them for a complex business process, there just not up to scratch.

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by fredmorrison

fredmorrison — Fri, 05 Nov 2010 18:29:14 +0000

Until I see SharePoint 2010 Enterprise workflows designed, deployed and run from Visual Studio 2010 using direct WF 4.0 activities, I stand by my earlier comments. If Microsoft wants to slipstream full WF 4.0 support into SharePoint 2010, that will be great, but something tells me not to hold my breath waiting for that to happen.

As for Windows 7 as a viable SharePoint 2010 development environment, I have two words that shoot that idea down: Active Directory. Only in a virtual machine environment running AD on a Server Operating System can I have the type of sandboxed (from an AD perspective) environment where I have my own private AD to use for testing and experimenting without affecting anyone else. If anybody knows how to do the same thing with Windows 7, I stand ready to be corrected, but somehow I doubt that’s going to happen.

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by Gertjan

Gertjan — Fri, 05 Nov 2010 15:53:50 +0000

Sharepoint 2010 can also run on forinstance a Windows 7 Professional laptop for development mode. No need for a server. Check http://msdn.microsoft.com/en-us/library/ee554869.aspx

Sharepoint 2010 will support .NET 4.0, Microsoft is working on this, however it is not yet available

Sharepoint 2010 however already can work with WF 4.0, WF 4.0 is build on .NET 4.0 but you can run WF 4.0 by calling a WCF host (external site from Sharepoint).

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by fredmorrison

fredmorrison — Mon, 28 Jun 2010 11:07:10 +0000

From what I’ve heard unofficially from various low-level people at Microsoft, the SharePoint team could not bank on .Net 4.0 (which includes WF 4.0) being ready on time for the planned release of SharePoint 2010, so they went with .Net 3.5 SP1 instead. Again, this is unofficial from only a small number of people at Microsoft, none of whom is directly involved in the official SharePoint team at Microsoft. This means that all the .Net 4.0 “goodness” will have to wait for the next release of SharePoint. Throw in the fact that companies and (especially) governments are slow to upgrade their IT infrastructure and you’re talking at least four years before WF 4.0 becomes usable in a practical sense.

Comment on Initial Thoughts On SharePoint 2010 Workflow Development Using WF 4.0, Visual Studio 2010 by Bill Melater

Bill Melater — Sun, 27 Jun 2010 02:23:59 +0000

How is it that windows is able to incorporate the latest releases of .NET but SharePoint is not. It always seems that the SharePoint team is off doing something on their own.

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

noactive — Mon, 11 Jan 2010 17:27:39 +0000

Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) .Thanks for nice post.I added to my twitter.

Comment on MSDN Workflow Stuff by shaz

shaz — Sat, 09 Jan 2010 19:12:47 +0000

Hey fred,

I need to replicate task acitivity for a group of people.I used the replicator(parallel),WSS task activity as you described here http://social.msdn.microsoft.com/forums/en-US/sharepointdevelopment/thread/0a395dd8-ba02-4796-af30-b3f942eb3a63.The tasks get created perfectly fine.But onTaskChanged event does not fire.

Can you please send me a working sample code?

And i needed to use a custom task edit form , how could i include the createTaskWithContentType activity’s funtinality within the wssTaskActivity?

Comment on Windows 7 and SharePoint 2010 – Broken As Designed (B.A.D.) by Nyath Maxwell - MCTS

Nyath Maxwell - MCTS — Sun, 03 Jan 2010 10:42:17 +0000

VM Ware is the only way to go on ANY platform! I have had nothing but problems from Virtual PC and DUMPED it completely about 6 months ago when it broke my lab environment completely!