This project is read-only.

Getting Started

Web Service Software Factory v3 Community Drop (build 38)

27 April 2007

Assumptions:
  • 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 evalute 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.

Contents

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

The goal of this drop is to get your feedback on how the code generated from model elements (shapes) is applied to the appropriate projects. In past builds, all of the code gets generated into a single project. This is the first drop that introduces Project Mapping. Click here to learn about how the code generation service uses IArtifactLinks and the Project Mapping Manager (PMM) to put source code in the right place.

System requirements

Installation instructions

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


After ensuring the machine meets the system requirements above (install them in the order they appear), following these steps:

 Information:
 While these installation steps may seem tedious (and yes, we will be streamlining them
in future drops) you can be assured that you will be introduced to a number of concepts
all factory authors are (or should be) familiar with.

 Please follow these steps exactly. It's not difficult, but it is a bit fragile at this
point. When you get to the end, if things don't work, just reset your experimental hive
and try again. Also be sure you have all of the system requirements installed before
beginning these steps.

  • Uninstall any previous v3 community drops (source or other). Verify with the Control Panel's Add/Remove Programs utility.
  • Reset the experimental hive (under Start -> Programs -> Visual Studio 2005 SDK -> 2007.02 -> Tools)

 Information:
 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 instace of VS you use everyday).
During testing, a different instance of Visual Studio (we'll call it the experimental
instancee of VS) is used and it only operates on the experimental hive. See
http://msdn2.microsoft.com/en-us/library/bb166560(VS.80).aspx 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.

  • Install the ServiceFactorySource-v3b38.msi into a short path name (i.e. C:\Projects\WssfV3Src)
    • If you are using the Profession edition of Visual Studio 2005, deselect the VSTS tests since you won't be able to open them.
    • On the last step, check the box to open the target folder.
  • Create a strong name key, called ProductKey.snk, and get its public key token:
    • Copy the CreateProductKey.bat file from where you extracted the ZIP file into the source folder.
    • Open a Visual Studio command prompt and navigate to the folder where you installed the source (C:\Projects\WssfV3Src)
    • Run the CreateProductKey.bat file
    • Copy this public key token (16 characters) to your clipboard
  • Open a normal (non-experimental) instance of Visual Studio 2005
    • If you are using Windows Vista, you must open VS using Administrator rights.
    • Do not open the Service Factory Guidance package.sln file in it - just open Visual Studio for now
  • Find and replace ALL files in the source folder (including subfolders) and replace ##CustomPublicKeyToken## with the public key token on your clipboard.
This is how your dialog should look
  • You should find/replace 20 occurances.
  • If you did not install the VSTS tests, you will only find/replace 18 occurances.

 Information:
 In future builds, we'll try to automate the creation of the strong name key and apply
the new token to the solution for you.

  • Open the Service Factory Guidance package.sln file from your souce installation folder using the already-opened instance of Visual Studio.
  • Attach the Clarius Software Factory 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 choose OK
    • Select the Close button on the Guidance Package Manager dialog
  • Change the build option from "Debug" to "Release". If you don't do this, you are likely to see a LOT of assert dialogs while you are using the designers.
  • 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
  • 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. If you try it using the normal instance of VS, it will fail with errors - as it should.

 Information:
 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

 Known Issue:
 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.


Be sure to accomplish these steps in order
  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

The only new thing in this drop is the ability to map model elements to specific Visual Studio projects. Click here to learn about how the project mapping functionality is implemented.

Walkthrough of using this drop

This walkthrough is a relatively simple exercise 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 questionaire - 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 create a data contract model from XSD documents.
  • The ability to create a service contract model from a WSDL document.
  • Model validatation: not all of the model validation will be finished, but more than what is in there now, which is none ;)

Last edited Apr 28, 2007 at 1:39 AM by donsmith, version 4

Comments

No comments yet.