State machine WF and WCSF Pageflow

Oct 24, 2007 at 5:10 PM
From the documentation I read that the WCSF Page flow is a specialised version of a state machine workflow. What I'm hoping to do is to use a 'standard' state machine workflow to provide the plumbing for my application, and then use a Pageflow when suitable to manage navigation.

What I'm curious about is can both of these share the same persitance and, in the case of the wf tracking, store?

Thanks
Apr 23, 2008 at 1:10 AM
PageFlow does use the WF tracking store. However, that PageFlow would be a different instance than you 'standard' workflow and would persist separately.
Apr 24, 2008 at 12:51 PM
I'm new to WWF and I want to use the Page Flow Application Block.
I followed the trail of breadcrumbs to the WCSF contrib where the code and templates ended up living.
How do I install the templates and use them?
I have the hands-on lab, from WCSF 2.0, to learn how to use the Page Flow Application Block but I cannot see the recipe or use it at all.
Apr 24, 2008 at 2:45 PM
ScottSuppan,

Reads as if you are mixing up two things. In order to use the Page Flow Application Block you need to install the Web Client Software Factory first. Info here: http://www.codeplex.com/websf

Looks at the Releases tab for the latest version.
Apr 24, 2008 at 5:47 PM
The problem is that the Page Flow Application Block is not included in the Web Client Software 2.0 February 2008 Release. In order to use the Page Flow guidance package, you must download the latest Web Client Software Factory Contrib source. I downloaded the source, but had a problem running the Page Flow Guidance Package setup (more information can be found here: http://www.codeplex.com/wcsfcontrib/WorkItem/View.aspx?WorkItemId=10038). If anybody has any help on this issue, please comment here or on the issue page.
Apr 24, 2008 at 6:17 PM
Thanks for the info LeonK but I already installed the WCSF. The problem is that I don't have the template/Recipe available to me after running the .msi to install the WCSF. Is there something I'm missing? I followed the trail of breadcrumbs which lead me to the WCSF Contrib source. I downloaded this source and unzipped it. However, I didn't know what to do next. ledijpagezep indicates somekind of setup program. Was I supposed to run some setup program after downloading the source? I could really use some guidance here. Thanks.

I'm using the hands-on lab and I'm stuck on Task 2. I cannot create a Page Flow Project via the wizard/Recipe.
Apr 24, 2008 at 7:13 PM
After you unzip the source, navigate to the following folder "Trunk\src\GuidancePackages\Pageflow." Open the "Pageflow Guidance Package (VSTS Tests).sln" solution in VS 2008. If you are prompted to connect to Team Foundation Server, you can click "Cancel" and select "OK" when asked if you want to "Go Offline." Build the solution. The "PageflowPackageSetup" project will generate an MSI and setup file (located in a "Release" or "Debug" folder depending on if you build for Release of Debug) that you are supposed to run in order to install the Page Flow Guidance Package. I'm curious to find out how the install goes for you.
Apr 25, 2008 at 3:33 AM
Edited Apr 25, 2008 at 4:45 AM
Has anyone had any success in building with the powershell scripts provided in the page flow?


Install was a success once I used the solutions to build the code. Could not get the powershell scripts to work.
Apr 25, 2008 at 2:01 PM
ledjpagezep,

Thanks for the advice. I followed your instructions.
I wasn't asked to hook up to the Team Foundation Server. I was, however, informed about some security risks. Strange, eh?
I attempted to build the solution and got 42 errors. Is this what you get?
There's a bunch of problems, some of which are assembly references.
When I unzipped this package, should I have unzipped it to a subfolder of the WCSF package that I had unzipped earlier?
It seems to me that the WCSF package is where all of the .dll's and namespaces are declared.

I'm also using VS2008 and not VS2005 to build this. So naturally, VS2008 prompts me to convert the project into something compatible.
Apr 25, 2008 at 2:02 PM

ledjpagezep wrote:
After you unzip the source, navigate to the following folder "Trunk\src\GuidancePackages\Pageflow." Open the "Pageflow Guidance Package (VSTS Tests).sln" solution in VS 2008. If you are prompted to connect to Team Foundation Server, you can click "Cancel" and select "OK" when asked if you want to "Go Offline." Build the solution. The "PageflowPackageSetup" project will generate an MSI and setup file (located in a "Release" or "Debug" folder depending on if you build for Release of Debug) that you are supposed to run in order to install the Page Flow Guidance Package. I'm curious to find out how the install goes for you.


I replied earlier. Hope you see my reply.
Apr 25, 2008 at 3:05 PM
ScottSuppan,

I was able to build the solution. The problem I had was successfully running the installer after the solution is built. The "Pageflow Guidance Package (VSTS Tests)" solution is independent of the WCSF 2.0 package. Which assembly references are you missing? The PageFlow.WorkflowFoundation assembly references the Windows Workflow Foundation assemblies (which are part of .NET 3.0). If you do not have .NET 3.0 installed, this could be causing the problem.

I am confused about "convert the project into something compatible." The "Pageflow Guidance Package (VSTS Tests)" solution should already contain Visual Studio 2008 projects.
Apr 25, 2008 at 3:13 PM
u40135,

Do you mind sharing the MSI and setup files that you built? I really want to get the Page Flow Guidance Package to work!
Apr 25, 2008 at 6:15 PM

ledjpagezep wrote:
ScottSuppan,

I was able to build the solution. The problem I had was successfully running the installer after the solution is built. The "Pageflow Guidance Package (VSTS Tests)" solution is independent of the WCSF 2.0 package. Which assembly references are you missing? The PageFlow.WorkflowFoundation assembly references the Windows Workflow Foundation assemblies (which are part of .NET 3.0). If you do not have .NET 3.0 installed, this could be causing the problem.

I am confused about "convert the project into something compatible." The "Pageflow Guidance Package (VSTS Tests)" solution should already contain Visual Studio 2008 projects.



ledjpagezep,

I thought that when I install VS2008, it will install the .NET 3.5 framework with it. I should be covered by that - eh?

The compatibility issue that I spoke about earlier is a one-time conversion when you open up a solution or project that was created in VS2005. When you do this, VS2008 will prompt you to convert it to VS2008.
Apr 25, 2008 at 9:48 PM
Good point about VS2008 and .NET 3.5 Framework. I guess .NET Framework isn't the problem. What assemblies are you having problems with?
Apr 28, 2008 at 10:44 PM

ledjpagezep wrote:
Good point about VS2008 and .NET 3.5 Framework. I guess .NET Framework isn't the problem. What assemblies are you having problems with?


I've got a question for you. Am I supposed to run IZARCC.exe at all? What does this do?
Apr 28, 2008 at 10:51 PM

ledjpagezep wrote:
Good point about VS2008 and .NET 3.5 Framework. I guess .NET Framework isn't the problem. What assemblies are you having problems with?


Here's a smattering of my build problems with respect to the guidance package:
Error 1 The type or namespace name 'Practices' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackageInstaller\InstallerClass.cs 17 17 PageflowPackageInstaller
Error 2 The type or namespace name 'ManifestInstaller' could not be found (are you missing a using directive or an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackageInstaller\InstallerClass.cs 25 35 PageflowPackageInstaller
Error 3 The type or namespace name 'Library' does not exist in the namespace 'Microsoft.Practices.RecipeFramework' (are you missing an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowProjectPage\CreatePageFlowProjectPagePresenter.cs 5 43 PageflowPackage
Error 4 The type or namespace name 'WizardFramework' does not exist in the namespace 'Microsoft.Practices' (are you missing an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowProjectPage\CreatePageFlowProjectPage.cs 8 27 PageflowPackage
Error 5 The type or namespace name 'CustomWizardPage' could not be found (are you missing a using directive or an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowProjectPage\CreatePageFlowProjectPage.cs 18 54 PageflowPackage
Apr 28, 2008 at 11:30 PM

ScottSuppan wrote:

ledjpagezep wrote:
Good point about VS2008 and .NET 3.5 Framework. I guess .NET Framework isn't the problem. What assemblies are you having problems with?


I've got a question for you. Am I supposed to run IZARCC.exe at all? What does this do?


Ok...I downloaded and installed Guidance Automation Toolkit Enhancements.
This reduced the compilation errors of the contrib to 25 errors.
Here's what I get now (a sample):
Error 1 The type or namespace name 'WizardFramework' does not exist in the namespace 'Microsoft.Practices' (are you missing an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowProjectPage\CreatePageFlowProjectPage.cs 8 27 PageflowPackage
Error 2 The type or namespace name 'CustomWizardPage' could not be found (are you missing a using directive or an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowProjectPage\CreatePageFlowProjectPage.cs 18 54 PageflowPackage
Error 3 The type or namespace name 'WizardFramework' does not exist in the namespace 'Microsoft.Practices' (are you missing an assembly reference?) C:\Documents and Settings\Owner\My Documents\Scott\wcsfcontrib-17811\Trunk\src\GuidancePackages\Pageflow\PageflowPackage\CustomWizardPages\CreatePageFlowPage\CreatePageFlowPage.cs 10 27 PageflowPackage

Where do these assemblies come from?
Apr 28, 2008 at 11:58 PM

ScottSuppan wrote:

ledjpagezep wrote:
Good point about VS2008 and .NET 3.5 Framework. I guess .NET Framework isn't the problem. What assemblies are you having problems with?


I've got a question for you. Am I supposed to run IZARCC.exe at all? What does this do?


ledjpagezep,

Eureka! I got it to work. The .msi built and installed!
I figures out the issue. I had the wrong or incomplete set up of Guidance Automation Extensions.
Once I fixed this, I got no complie issues.
Thanks for your help!
Apr 29, 2008 at 1:24 PM
Did anyone have any problems installing the Enterprise Library 3.1?
Everytime I run the .msi for it, it encounters a problem installing one of the assemblies and then rollsback the entire installation.
Apr 29, 2008 at 2:05 PM
Strange problem with the Enterprise Library 3.1 installer. It will encounter an error if you have the Guidance Automation Extensions installed. Your best bet is to uninstall Guidance Automation Extensions, install Enterprise Library, then reinstall Guidance Automation Extensions.