Ezequiel Jadib’s Blog

OK, we have installed Smart Client Software Factory in Orcas Beta 2, but.. how about Web Client Software Factory?

In this post, I will detail the steps you have to follow in order to use WCSF June 2007 with Orcas Beta 2.

1. Install Guidance Automation Extensions Technology Preview (July 2007 Release for Visual Studio 2005 and Visual Studio Beta 2).
2. Download and install Orca MSI editor (which is distributed with the Windows SDK). The Orca MSI Editor is a table-editing tool that can be used to edit your .msi files. If you want to learn more about this tool, please visit this link.
   Note: If you don’t want to download the Windows SDK, a guy published the Orca.msi tool (Download from this place at your own risk).
3. Open Orca MSI editor and then go to File > Open….Select the WCSF MSI file (Web Client Software Factory - June 2007.msi).
     
4. Select the RegLocator table from the tables list.
    
5. Modify the following key values (replace the 8.0 with 9.0 in the paths) from this table:
   • FindVSInstallDir
   • VisualStudioInstallRegistry
   • VistualStudioHelpRegistrySearch

   This is how it should look after replacing these values
   

6. Save the changes.
7. Install Web Client Software Factory June 2007.
   

Known Issues

WAP and Non-WAP Issues

• Runtime exception when the project is executed
   

  This is an old issue which was discussed in this thread. In order to fix this you have to modify the line 107 of the WebClientApplication.cs file (under CompositeWebApplicationBlock\CompositeWeb) to:

  if (HttpRequestHelper.IsHandledByPageHandlerFactory(context.Request.Url.ToString()) && context.Handler != null) 
  

• Build fails after adding a Foundational or Business module with Test project

  In order to fix this you have to modify the following files inside WebClientSoftwareFactoryPackage inside Templates folder:

  • \Module.Tests.VB\*.vbproj
  • \Module.Tests.C#\*.csproj

Change:

<Reference Include=”Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL”>
</Reference>

For:

<Reference Include=”Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL” /> 

Non-WAP specific issues

• A dialog box is shown after the creation of the solution
   

  If you click Yes, you can go on without problem, but if you want to avoid this dialog box everytime you create a Web Client solution you will have to add the missing tags in the Web.config template.

• Website is not being recognized as a WebProject

  This cause the following issues:

  • An exception occurs after Adding a Business Module
    

  • In the Add Foundation Module window the website dropdown is empty so the Finish button is disabled. No Foundational Module can be added to the web client solution.
    

  • The Add View (with Presenter) menu option is not visible.
     

In order to fix these you have two options:

• Closing and reopening the solution (it's just a workaround :))
• Update the CreateWebClientSoftwareSolutionCommon.xml recipe by adding the following in the Actions section:

  <Action Name=”SetIsWebProject” Type=”AddProjectGlobalsEntryAction” PropertyName=”IsWebProject” PropertyValue=”True”>
        <Input Name=”Project” RecipeArgument=”WebUIProject” />
  </Action>
  
  

  You should also modify the vwd.webinfo file by removing the IsWebProject=”true” property:

  <?xml version=”1.0″ encoding=”UTF-8″?>
  <!– Visual Studio global web project settings.–>
  <VisualWebDeveloper>
  <Globals>
      <UserProperties />
  </Globals>
  </VisualWebDeveloper>
  
  

Hope you find this guidance useful. Feel free to visit us at Codeplex Forum to give us feedback.

Attached you fill find a zip file that contains the files modified. Just unzip this on %program files%\Microsoft Web Client Factory\WCSF Guidance Package. Click Yes to All to replace the existing files.
Note: The zip does not includes the modified Composite Web Application Block.

Important: Keep in mind that this is just a workaround so use these steps at your own risk. This guidance is provided “as is” without warranty of any kind.

Attachment: WCSFOrcas.zip