This project is read-only.

Getting Started

Web Service Software Factory v3 Community Drop (build 117)

  • You have a real job and don't have an infinite amount of time to evaluate this drop.
  • You are interested in influencing the direction of Service Factory v3.
  • You are interested in monitoring the progress of Service Factory v3.
  • The Service Factory team respects your time and doesn't want to waste it.
  • We intend to be transparent about the status and scope of the project.
  • We are committed to ensure Service Factory will meet your needs.

With that in mind, we have created these set of documents. They are here to help YOU save time while you evaluate and provide feedback about this drop. If this is not useful, please let me know. Because putting all of this together is definitely an investment in time and energy that I could be doing something else that is potentially more useful. Thanks.


Goals of this Drop
System Requirements
Installation Instructions
Uninstallation Instructions
List of New Things You Can Do
Walkthrough of Using this Drop
What Will Go in the Next Drop

Goals of this Drop

This Web Service Factory: Modeling Edition community release is now available for you to review using a binary installer. The goal of this drop is to get your feedback before we are feature complete. While we’re not yet finished, we have done more work on the host designer. We also have most of the redesign finished on the “Import WSDL” and “Import XSD”. While there are still some bugs, we would love to hear your feedback on our approach.

About this Drop

This community release is available in two forms:
  • Binary Installer. This allows you to go through the main walkthrough.
  • Source Code Installer. This allows you to go through the main walkthrough and the extensibility walkthroughs, in addition to viewing the source code.
You can only install one or the other, not both. If you only want to evaluate and provide feedback, you don’t need to install the source code, only the binaries. The disadvantage is that you will not be able to do the extensibility walkthroughs, just the basic walkthrough. If you want to review the code and do the extensibility walkthroughs, you will need to install the source code. If you decide that you want to review the source code after installing the factory using the binary installer, you must follow the uninstallation instructions and then reinstall using the source code installer. There are different system requirements and installation instructions depending on which installer you choose to install.

General System Requirements

Additional System Requirements for Binary Installer

Additional System Requirements for Source Code Installer

  • Guidance Automation Extensions (GAX) 1.2 (you should already have this version installed, if you do not, you cannot use the Source Code Installer)
  • Guidance Automation Toolkit (GAT) 1.2 (you should already have this version installed, if you do not, you cannot use the Source Code Installer)
  • Clarius SFT – Feb 2007 CTP or Clarius SFT - June 2007 CTP.

Installation Instructions

Known Issue
If you already have a DSL installed that uses .servicecontract, .datacontract, or *.host as the file extensions for its models, installing this release will overwrite your existing DSL. We don't suspect this will impact many people, but we thought it would be safe to mention it before you install. This is a known issue with the DSL toolkit installers.

Installation Instructions for Binary Installer

  1. To install the Service Factory: Modeling Edition binaries
  1. Uninstall any previous v3 community drops (source or other). Verify with the Control Panel's Add/Remove Programs utility.
  2. Click on the Binary MSI for this release and install the binaries to your preferred location.

Installation Instructions for Source Code Installer

For this release, you need to have the previous version of GAT/GAX installed (version 1.2). If you do not, you should install the binary instead of the source code for this release.
  1. To install the Service Factory: Modeling Edition source code
  1. Reset the experimental hive (under Start -> Programs -> Visual Studio 2005 SDK -> 2007.02 -> Tools).
  2. Click on the Source Code MSI for this release. Install the Service Factory into a short path name (i.e. C:\WssfSrc). If you are using the Professional edition of Visual Studio 2005, deselect the VSTS tests since you won't be able to open them.Complete the following post-installation activities. These have been automated into a build task.
    1. Open a Visual Studio Command Prompt and navigate to the folder you installed to. If you are using Windows Vista, this should be opened as an administrator.
    2. Execute the build task by entering “msbuild PostInstall.proj”
    3. Close the command prompt window.
    1. Open the Service Factory Guidance package.sln file from your source installation folder using a normal (non-experimental) instance of Visual Studio.
    2. Attach the Clarius Software Factories Toolkit guidance package to the solution. To do this:
      • On the Tools menu, select "Guidance Package Manager", select the "Enable/Disable Packages ..." button, check the "Clarius MetaFactory" and click OK.
      • Select the Close button on the Guidance Package Manager dialog
      • Rebuild the entire solution. To do so, right-click on the solution and choose "Rebuild Solution."
      • Right-click on the "Service Factory Guidance Package" project and select "Register Guidance Package". Be sure to register in the "Regular & Experimental" hive.
        1. This drop has now been installed. The important thing to remember is anytime you wish to create* Service Factory v3 solution*, you must do so with an experimental instance of Visual Studio (under Start -> Programs -> Visual Studio 2005 SDK -> 2007.02 -> Tools -> Start Visual Studio 2005 under Experimental hive). If you try it using the normal instance of Visual Studio, it will fail with errors - as it should. In other words, if you are building from the source, you should be working in the experimental hive.

      The experimental hive is a part of the registry - provided by the VS SDK - that is designated to test Visual Studio extensions (like DSLs) without the danger of corrupting the main registry hive that Visual Studio uses (the instance of VS you use every day). During testing, a different instance of Visual Studio (we'll call it the experimental instance of VS) is used and it only operates on the experimental hive. See for more information. This step ensures you start from a clean slate. If you have been doing other work with the DSL toolkit in the experimental hive, this will erase the registrations of those components.

      We have tested this drop in a side-by-side installation with the December release of Service Factory and did not encounter any problems before or after we uninstalled this drop. You should be okay if you already have v2 installed.

      Uninstallation Instructions

      Uninstallation Instructions for Binary Installer

      To uninstall the Web Service Software Factory:
      1. In the Control Panel, double-click Add or Remove Programs.
      2. In the Add or Remove Programs dialog box, select Web Service Software Factory: Modeling Edition Community Drop 7.
      3. Click Remove.
      4. Using Windows Explorer (or a command prompt), delete the folder you installed the source into. By default, the folder is C:\Program Files\Microsoft Service Factory V3.

      Uninstallation Instructions for Source Code Installer

      Known Issue
      If you have installed the source code, when you build the Service Factory v3 solution, some DLLs will be copied to the public assemblies folder and some will be registered in the GAC. The uninstallation steps below will not undo these actions. We will provide more details and complete uninstallation instructions in a future community drop.

      To uninstall the Web Service Software Factory:
      1. Open the source solution in a normal instance of Visual Studio
      2. Unregister the Service Factory Guidance Package (right-click on the project and choose "Unregister Guidance Package")
      3. Reset the Visual Studio 2005 experimental hive.
      4. Using Windows Explorer (or a command prompt), delete the folder you installed the source into.

      List of New Things You Can Do

      • Install the Service Factory without having to build from source the code.
      • You now have the ability to model how the service will be hosted using the new host designer. This new designer also allows you to model the endpoints, clients, and their proxies. This designer can also expose the service as an ASMX service.
      • You can import existing WSDL documents and create messages based on existing XSD files.

      Walkthrough of Using This Drop

      This walkthrough is a relatively comprehensive set of exercises that will give you the opportunity to see everything this drop offers without you having to rely on your own devices to find everything. We've also included a little rationale for why we did things the way we did, what is not finished yet, and what we know will change, and what we'd like your input on. We did this so we can minimize the time you have to spend with it while also giving you a very explicit way of providing your feedback. Before you get started, please open this text questionnaire - you can quickly fill it out while you're cruising through the walkthrough. Okay, now you can complete the walkthrough.

      What Will Go in the Next Drop

      Well, it might not go in the very next one, but definitely in a future one :)
      • The ability to expose WCF services from the host designer.
      • The ability to generate client proxies from the host designer.
      • We will update to GAX 1.3 and Enterprise Library 3.1
      • We will have a way to rebuild an MSI for a modified Service Factory

Last edited Aug 13, 2007 at 10:46 PM by donsmith, version 9


mattortiz Sep 10, 2007 at 9:34 PM 
I certainly appreciate the work the P&P folks have been doing, specifically, regarding ent lib and the service factory. However, with the drop of Visual Studio Orcas, .NET 3.5 and Linq to SQL, inparticular, I find it difficult to pull myself backwards to check out the work being done on this drop of the service factory as it only works in VS 2005. Please make it a priority to support Orcas and Linq. I see this drop introduces support for GAX 1.3 which is certain to be a step in that direction: Right!?. In order for me to commit to too much time evaluating I'd need to be sure it will provide support in those areas. Any feedback and committments here would be greatly appreciated.

Thanks again for your work - it is appreciated.