Installing the Web Client Software Factory

The Web Client Software Factory contains a variety of software assets, such as reusable code components, documentation, reference implementations, and tools, including wizards, code generators, and visual designers.

Summary of Installation Steps

Installing Web Client Software Factory - January 2007 release

Use the following steps to install the Web Client Software Factory and its prerequisites. These steps assume that you do not have a previous version of the factory installed.
  1. Install the Guidance Automation Extensions (February 2007) CTP Release.
  2. Install the Guidance Automation Toolkit (February 2007) CTP Release.
  3. Install the .NET Framework 3.0 and the Visual Studio 2005 Extensions for Windows WorkFlow Foundation.
  4. View the Web Client Software Factory Documentation (optional).
  5. Install the Web Client Software Factory - January 2007 release.


--------------------------------------------------------------------------------------------------

To run the reference implementation you need to install two databases by running the SetUpDatabase.cmd script. To run the Guidance Package, you need to copy the Composite Web Application Block DLLs to the location with the Enterprise Library DLLs. This allows the recipes to create the references to these DLLs.
  • Run the MSI and install the WCSF Guidance Packages, Documentation, and Source Code Installer

To run the Reference Implementation

To install the databases in SQL Server Express
  • Run the SetUpDatabase.cmd script in the RI1\Scripts folder.
  • Build and run the reference implementation using the GlobalBank.Commercial.EBanking.sln.

To install the databases in SQL Server 2005 or SQL Server 2000
  • Edit the command file SetUpDatabase.cmd in the RI1\Scripts folder.
  • Locate the following line:
  SET serverName="(local)\SQLEXPRESS"
  • Replace the string "(local)\SQLExpress" with your SQL Server instance name. If you are using the default SQL Server instance, use "localhost".
  • Save and run the command file.
  • Open the solution file RI1\GlobalBank.Commercial.EBanking.sln.
  • Open the configuration file Web.config located in the WebUI Web site root folder.
  • Locate the <connectionStrings> section and update the Data Source parameter of the RI_SqlConnection and the PageFlowPersistanceStore connection strings to point to the SQL Server instance where you installed the reference implementation database.
  • Locate the <hostingWorkflowRuntime> section and update the connectionString parameter of the SqlWorkflowPersistenceService service configuration to point to the SQL Server instance where you installed the reference implementation database.
  • Build and run the reference implementation using the GlobalBank.Commercial.EBanking.sln.

To run the QuickStarts

  • Run the SetUpDatabase.cmd script in the ..WCSF Source\QuickStarts\Scripts folder to setup the SQLExpress database for the Reference Implementation

To install the database in SQL Server 2005 or SQL Server 2000
  • Edit the command file SetUpDatabase.cmd located in the script folder of the QuickStarts solution.
  • Replace all instances of the string "(local)\SQLExpress" with your SQL Server instance name. If you are using the default SQL Server instance, use "localhost".
  • Select the QuickStart that you want to Run
    • Module QuickStart: Compile and build the QuickStart using the ModuleQuickstart.sln in the WCSF Source\QuickStart\Module folder
    • Object Container Data Source Quickstart: Compile and build the QuickStart using the ObjectContainerDataSourceQuickstart.sln in the …WCSF Source\QuickStart\ObjectContainerDataSource folder
    • PageFlow QuickStart: Compile and build the QuickStart using the PageFlowQuickstart.sln in the …WCSF Source\QuickStart\PageFlow folder
    • PageFlow With Shopping Cart QuickStart: Compile and build the QuickStart using the PageFlowWithShoppingCartQuickstart.sln in the …WCSF Source\QuickStart\PageFlowWithShoppingCart folder
    • ViewPresenter QuickStart: Compile and build the QuickStart using the ViewPresenterQuickStart.sln…WCSF Source\QuickStart\ViewPresenter folder

To run the Recipes in the Guidance Package

  • Compile and build the Guidance Package
  • Using Visual Studio, open and build the solution file WebClientFactory Guidance Package.sln in the …WCSF Source\GPs\WebClientFactory folder
  • Use the Guidance Package Manager to enable the Guidance Package Development guidance package.

Note: You must do this before you can use the Register Guidance Package, Quick Register, 
and Unregister Guidance Package recipes.


Note: You can find the Guidance Package Manager under the Tools menu.

  • In Solution Explorer, right-click the project named WebClientFactoryPackage, and then click Register Guidance Package.
  • To test the Recipes were Successfully Registered
    • Open a new instance of Visual Studio. In this new instance, create a new project using using the WebClient Software Factory Solution template from the Web Client Software Factory Development guidance package to create a new solution.

To run the PageFlow Designer

The application block contains custom Windows Workflow activities that you can use to define your page flows. You drag these controls from the Toolbox onto the design surface to create a page flow definition.
  • To add the custom controls to the Visual Studio Toolbox
    • Open the Toolbox in Visual Studio and right-click the Data tab in the Toolbox and select Choose Items.
    • In the .NET Framework Components tab, click Browse. Navigate to the folder that contains the assembly Microsoft.Practices.PageFlow.WorkflowFoundation. dll, select the assembly and then click Open.
  • Select the PageActivity and TransitionListenerActivity controls in the list of components and click OK.

Last edited Jun 21, 2007 at 5:56 PM by blainew, version 19

Comments

sheir Feb 22, 2008 at 4:29 PM 
There is a new version of GAX and GAT available -- Feb 2008 release.
http://blogs.msdn.com/tomholl/archive/2008/02/16/gosh-gat-gax-is-golden.aspx?CommentPosted=true#commentmessage

sheir Feb 21, 2008 at 7:22 PM 
Seems I was able to get the registation done finally BUT now trying to follow the
"To test the Recipes were Successfully Registered " steps and
when I do a Create New Project in VS2008;
I do not see the WebClient Software Factory Solution template from the Web Client Software Factory Development guidance package showing up.


Any ideas?

sheir Feb 21, 2008 at 4:06 PM 

I open the solution in VS2008
\WCSF Source\GP\WebClientFactory\WebClientFactory Guidance Package.sln
Got a lot of reference errors about various Microsoft.Practice DLLs;
which I fixed.
Got the solution to build without errors.

I followed the instructions in the following link
http://staff.southworks.net/blogs/ejadib/archive/2007/10/08/How_2D00_To_3A00_-Web-Client-Software-Factory-_2800_WCSF_2900_-_2600_-Visual-Studio-Orcas-Beta-2.aspx


I tried to follow the instructions on this page about
"To run the Recipes in the Guidance Package"

Got the solution to build but Tools -> Guidance Package Manager is disabled!

Any ideas on how to get this working with VS2008??

sheir Feb 21, 2008 at 3:32 PM 
For all the errors about LoaderException, it might be a result of having VS2008 installed on your system.
I had only VS2003 and VS2008 and ran into that issue with the .msi files.

The fix was found at the following link
http://staff.southworks.net/blogs/ejadib/archive/2007/10/08/How_2D00_To_3A00_-Web-Client-Software-Factory-_2800_WCSF_2900_-_2600_-Visual-Studio-Orcas-Beta-2.aspx

Sarbagya Jan 23, 2008 at 9:20 AM 
Hi,
I have problem install in web client software factory, During a installation it show an error message

Unable to get installer types in the c:\program files\Microsoft Visual Studio 8\Common7\ide\PublicAssemblies\WebClientFactoryPackageInstaller.dll assembly.-->Unable to load one or more of the requested types.Retrieve the LoaderExceptions property for more information

How can i solved this problem. I am using VS2005 Professional Edition on Windows XP SP 2

Hope to help from you guys

Regards and Metta,
Sarbagya

KeithW Sep 25, 2007 at 2:44 PM 
You can remove “WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]” on line 15 to get the script to run on SQL 2000.

According to the SQL 2005 breaking changes page (http://msdn2.microsoft.com/en-us/library/ms143179.aspx) and listed under the ‘Indexed Views’ section:
When you create a unique clustered index on a view in SQL Server 2005, the IGNORE_DUP_KEY option must be set to OFF. This is the default setting. Setting IGNORE_DUP_KEY to ON could lead to indexed view corruption.
Drop the clustered index on the view and re-create it without specifying the IGNORE_DUP_KEY option.

The SQL 2000 books online state:

In relation to SQL server 6.x:
“The ALLOW_DUP_ROW and IGNORE_DUP_ROW clauses of the CREATE INDEX statement allowed data to be updated into tables with a unique index and without having to filter out duplicates first.”

In relation to SQL Server 2000:
No longer supported. Using either ALLOW_DUP_ROW or IGNORE_DUP_ROW in the CREATE INDEX statement generates a warning message. If there is no unique clustered index and there is a need to avoid duplicate rows, create a unique constraint on one or more columns other than the clustering key

KeithW Sep 25, 2007 at 2:30 PM 
As mentioned above and also experienced by me the PageFlowInstanceStore.sql doesn’t run on SQL 2000

jinnz Aug 21, 2007 at 2:32 AM 
Hi,

Can someone please give me proper instructions for Installing Web Client Software Factory - June 2007 release, the link on this page is to a msi file not a zip file that has reference implementation, SetUpDatabase.cmd etc. I ran the guidance pakages fine but the Web Client Software Factory msi is returning an error "Unable to get installer types in the c:\program files\Microsoft Visual Studio 8\Common7\ide\PublicAssemblies\WebClientFactoryPackageInstaller.dll assembly.-->Unable to load one or more of the requested types.Retrieve the LoaderExceptions"
I see the error above but no resolutions. I have windows vista, visual studio 2005 & 2008.
thanks

bc1016 May 22, 2007 at 5:38 PM 
Never mind, I reinstalled the guidance package source code and rebuilt it and now it's working fine. Nice work, except for the less-than-perfect installation instruction.

Question, is the web site generated by the factory AJAX enabled?

Thanks.

bc1016 May 21, 2007 at 8:48 PM 
Hi, after following the steps to install everything, I got an error when trying to use the Add View(with presenter) recipe. The error is a Recipe Framework error, it says " an exception occurred during the binding of reference or execution of recipe CreateView. Error was: An error happened while calling the value provider or evaluating the default value of argument ModuleInfos.. You can remove the reference to this recipe through the Guidance Package Manager." What could be the cause for this? I have XP and VS 2005 team edition. Thanks in advance.

sanguedemonstro May 11, 2007 at 12:31 PM 
hi! i'm really interested about WCSF, but the installers that i've downloaded in this site today, it's incompatible...

* i've not Team Suite, is that needed?
* apparently the GAT.msi, GAX.msi dont mix each other not even the WCSF.msi...
* the error msg: Unable to get installer types in the c:\program files\Microsoft Visual Studio 8\Common7\ide\PublicAssemblies\WebClientFactoryPackageInstaller.dll assembly.-->Unable to load one or more of the requested types.Retrieve the LoaderExceptions property for more information.


can somebody help or fix that .msi ?
what should i do?

thanks!
//sorry about my english

fraggle666 May 4, 2007 at 8:11 AM 
Is there anywhere that I can set the SetUpDatabase.cmd to run using sql server permissions, rather than windows authentication?

henkh Apr 16, 2007 at 6:31 PM 
There's also a "typo" in the last step ("To run the PageFlow Designer"). It says: "Select the PageActivity and TransitionListenerActivity controls in the list of components and click OK" instead of "PageActivity" that should be "PageState".

hhaugen Mar 22, 2007 at 11:03 PM 
Documentation is missing crucial step: Under "Install the Web Client Software Factory" there should be an explicit instruction to locate sourcecode.msi in the programfiles and run it. Otherwise you'll never find the stuff that is talked about in the next step (like SetupDatabase.cmd)

mugun Mar 16, 2007 at 9:36 AM 
Before i go futher friends,
"<b>System Requirements</b>
Supported Operating Systems: Windows Server 2003; Windows XP
Microsoft .NET Framework 2.0
Microsoft .NET Framework 3.0
Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation)"

Do i need Microsoft Visual Studio Team Suite installed in order to install this app? Currently I'm using MS Visual Studio 2005 Professional Edition.

mugun Mar 16, 2007 at 9:25 AM 
Hi friends, i got some weird error as below :

Unable to get installer types in the c:\program files\Microsoft Visual Studio 8\Common7\ide\PublicAssemblies\WebClientFactoryPackageInstaller.dll assembly.-->Unable to load one or more of the requested types.Retrieve the LoaderExceptions property for more information.

I have follow exactly the instruction of steps to install WebClientFactory but cant go futher with this error.Please guide me what i should do next.

Thanks in advanced

Singlewind Mar 15, 2007 at 9:57 PM 
Me too. Because our VS does not have Test Framework. I think removing these entries is fine.

MiltonWaddams Feb 27, 2007 at 4:36 PM 
Hi have the exact same issue as GShock above. Removing the reference allows me to build the app, but I don't like doing this. I've read through the install docs several times and I'm sure I didn't miss anything. Great product idea, but personally I think the install documentation and process needs more work.

GShock Feb 22, 2007 at 5:49 PM 
just wanted to add that my vs is pro edition but we also have architect version which has the testing tools in the ide. i removed the references to the QualityTools from the web.config and the reference app runs fine.

GShock Feb 22, 2007 at 5:11 PM 
can somebody help me out with this? so far i have been able to get through all the crappy instructions and all the bad download links and all the non-mentions of packages to install in order to run the reference implementation (hey, no complaints here!) :) however my reference implementation won't run as it is intendeded to run because i get this error when i build the solution:

Error 102 Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. C:\VS2005\Projects\WCSF Source\RI1\Source\Infrastructure\WebUI\Web.config 134

somebody been through this before can help? thanks in advance!

regards,

G-

tsramkumar Feb 20, 2007 at 7:13 PM 
The Database install script is good for SQL Server 20005 and doesn't work with SQL Server 2000. Do you guys have a script for SQL Server 2000?

DarkNite Feb 17, 2007 at 1:08 PM 
I have downloaded the WCSF documentation and extracted the two .chm files. When I try to view them I get a navigation failed message in the right pane. Why are these help files attempting to connect to the internet?

xianggao68 Jan 30, 2007 at 4:19 PM 
Can I install the MCSF on Windows Vista? If yes, what are the steps?

stephens336 Jan 16, 2007 at 9:41 PM 
pacha, I renamed the web file to web.msi and that worked fine.

pacha Jan 13, 2007 at 3:03 AM 
i downloaded the "Web Client Software Factory" and the file called "web" how can i install this, i cannot open it. I already have downloaded all others things you listed above.

blainew Jan 10, 2007 at 1:15 AM 
The installation instructions have been updated to reflect installing the factory with the msi.

miggro Jan 5, 2007 at 11:05 PM 
In the installation instruction for "Web Client Software Factory" under "To test the Recipes were Successfully Registered" documentations says:

"Copy the following assemblies to the..." and refers to "Microsoft.Practices.ObjectBuilder.dll".

I think this should read "Microsoft.Practices.CompositeWeb.EnterpriseLibrary.dll" because this is a dll that is needed (and missing) when creating a new solution. The "Microsoft.Practices.ObjectBuilder.dll" is already present in the directory.

ksantoshkumar83 Dec 26, 2006 at 2:22 PM 
why dont u make every thing as one package so that tester can just install it and can check its functionality