Installation Instructions for Source Code Installer When Using Visual Studio Professional Edition or Team Architect Edition

Retired Content

The Web Service Software Factory is now maintained by the community and can be found on the Service Factory site.

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies.
This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Retired: November 2011

The Service Factory: Modeling Edition source code does not compile and the guidance package does not register out-of-the-box with Visual Studio Professional Edition. This is because the WCF Semantic Code Analysis rules feature that comes with the Service Factory is not compatible with the Professional Edition of Visual Studio. You must make the following changes to the code to work around the issue and disable this feature.

To install the Service Factory: Modeling Edition

  1. Ensure that your computer meets the system requirements. You should install the requirements in the order they appear.
  2. If you have installed any previous Service Factory: Modeling Edition community drops, follow the Uninstallation Instructions to remove the previous version.
  3. If you are using Microsoft Vista, open the Visual Studio 2008 Command Prompt as an administrator and run devenv /setup.
  4. Reset the Visual Studio 2008 Experimental hive. On the taskbar, click Start, point to All Programs, point to MicrosoftVisual Studio 2008 SDK, point to Tools, and then click Reset the Microsoft Visual Studio 2008 Experimental hive.
  5. Ff650298.note(en-us,PandP.10).gifNote:
    The experimental hive is a part of the registry; it is provided by the Visual Studio SDK and 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 Visual Studio you use every day). During testing, a different instance of Visual Studio is used that operates only on the experimental hive. For more information about the experimental hive, see Experimental Build on MSDN. 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.

  6. Install the Web Service Software Factory source .msi file to the default location (C:\Projects\WssfSrc). If you choose a different location, you should install the source code to a directory with a short path name (for example, C:\Projects\WssfV4Src). This is due to the following known issue with respect to the length of file names:
  7. Ff650298.note(en-us,PandP.10).gifNote:
    Known Issue: Windows operating systems do not allow pathnames longer than 254 characters on non-NTFS partitions. Some applications such as Visual Studio enforce his constraint independent of the format of the partition. Because the Service Factory: Modeling Edition source code includes some long namespaces, which directly affect the names of the resource files during a build, we recommend installing to a short path name.

  8. Follow the steps in the wizard. If you are using the Professional Edition of Visual Studio 2008, remove the Visual Studio Team System tests because you will not be able to open them. On the last step, select the check box to open the new working folder.
  9. Run the build script that contains the post-installation activities:
    1. Open a Visual Studio Command Prompt and navigate to the folder where you installed the Service Factory (for example, C:\Projects\WssfSrc). If you are using Windows Vista, this should be opened as an administrator.
    2. Run the build task by entering msbuild PostInstall.proj.
    3. Close the command prompt window.
  10. Using a normal (non-experimental) instance of Visual Studio, open the Service Factory Guidance package.sln file from your source installation folder.
  11. Remove the Code Analysis project folder (or underlying project Microsoft.Practices.FxCopRules.WcfSemantic) from the solution.
  12. Remove the Code Analysis folder in Guidance Package/Service Factory Guidance Package/Recipes/CodeAnalysis folder.
  13. Open the Service Factory Guidance Package.xml file located under the Service Factory Guidance Package Project and comment out or remove the following line under the <Recipes> tag.
  14. <xi:include href="Recipes/CodeAnalysis/RunCodeAnalysisRules.xml"/>
    
    
  15. Open the Binding.xml file located under the Service Factory Guidance Package Project/Recipes/ folder and comment out or remove the following line under the <Actions> tag.
  16. <Action Name="RunCodeAnalysisRulesRef" Type="RefCreator" AssetName="RunCodeAnalysisRules"
                                                                    ReferenceType="AnyProjectReference" />
    
    
  17. Comment out the following line in Service Factory Guidance Package Files.wxs which is located in the Service Factory Guidance Package Setup project.
  18. <File Id="ID_ef985059_c088_4d5d_ba51_dc402ed29eb9" DiskId="1" Name="F0005.sfn" LongName="Microsoft.Practices.FxCop.Rules.WcfSemantic.dll" />
    
    
  19. Rebuild the entire solution.
  20. Attach the Guidance Automation Toolkit to the solution. To do this:
    1. On the Tools menu, click Guidance Package Manager.
    2. In the Guidance Package Manager dialog box, click Enable/Disable Packages.
    3. In the Enable and Disable Packages dialog box, select the Guidance Package Development check box, and then click OK.
    4. In the Guidance Package Manager dialog box, click Close.
  21. In Solution Explorer, right-click Service Factory Guidance Package, and then click Register Guidance Package. (This may take several minutes depending on the speed of your computer).
  22. After you successfully register the guidance package, close Visual Studio.

Show: