Known Issues
This page contains all of the issues the Service Factory team is aware of. An issue in this context can be a bug in the Service Factory or dependent component, or just something we think you should be aware of as you install, build, and use the factory. These issues are organized into sections so you will be able to associate an issue with the activity you were doing when you experienced the issue. Within each section the issues are ordered from most severe to least severe. We highly recommend you review at least the sections names in this document so you will know where you might run across issues. We also recommend you read the first general guidance section in its entirety so you can avoid many of the common issues.

General guidance to avoid many of the common known issues
  • Model dependencies. There can be a lot of dependencies between different models, model elements, and projects. If any of these dependencies become invalid, it can affect the experience of working with the models and generating code and cause unexpected behavior. See the Model Dependencies topic in the Service Factory documentation to understand where these dependencies exist.
  • Globalization. Due to cost and scope issues, extensive globalization and localization testing was not performed on the Service Factory. We tested enough to know that anyone intending to localize the factory will encounter some issues. When using certain non-ASCII character sets in model and model element names can cause unexpected behavior. The Service Factory team is willing to address this after the release if the demand justifies it.
  • Circular references. The Service Factory provides a great deal of control over how and where the code is generated. At times the factory will establish the project dependencies for you – other times you will have to establish them yourself. Depending on how the roles are assigned to model elements, circular dependencies can occur. Fortunately, Visual Studio provides a reasonable error message when this happens. Just be aware that the Service Factory isn’t able to protect you from them.

Installing the binary installer
1. DSL File Extensions (9535 & 9536): The DSL Toolkit, which is used by the Service Factory, only allows a file extension to be registered by a single DSL on a computer. The last DSL package to register a file extension will corrupt any previously existing packages that use that extension.
Workaround: Don’t install the Service Factory modeling edition if you have other DSLs installed that are using the .servicecontract, .datacontract, or .host file extensions. Also, don’t install other DSL packages that use these extensions after you have installed the Service Factory.
Applies To: VS2005, VS2008

2. Intermittent Registration (14523): An issue in the DSL Toolkit occasionally causes a DSL package to not get registered properly on Windows Vista. If after installation right-clicking on the Host Explorer or Service or Data Contract designers causes a dialog with the text "HRESULT E_FAIL has been returned on call to COM component" to appear then the DSLs have failed to register correctly.
Workaround: Shutdown Visual Studio and manually run devenv.exe /setup from the Visual Studio Command Prompt. Once it completes, restart Visual Studio and you should no longer be able to reproduce the error.
Applies To: VS2005

3. User-based Installation (14596): The Service Factory can only be installed once on a computer. This means it is not possible to perform the installation under more than one user account on a computer. We are not aware of any issues that prevent Service Factory from being used by more than one user account when it is installed.
Workaround: The installation is for all users (Machine scope) so this is the expected behavior by design.
Applies To: VS2005, VS2008

Starting Visual Studio
Factory Initialization (13484): The Service Factory contains a custom Visual Studio project called the Model Project. The purpose of this project is to hold all of the logical models for all of the services in the solution. Because it is a Visual Studio project, Visual Studio initializes it and all of its dependencies when you open Visual Studio. We are not aware of any problems caused by this initialization, but given the time, we would have liked to ensure only the bare minimum was being loaded when Service Factory is not being used. Without any change, it is initializing more than it actually needs to.
Workaround: None.
Applies To: VS2005, VS2008

4. XAML Power Toys can break initialization: If you have the XAML Power Toys installed, it can cause your Service Factory installation to stop initializing correctly. This issue has been verified by at least 4 users, and in at least one case, removing the XAML Power Toys from the Visual Studio add-ins (and restarting VS) fixed the problem - uninstallation of the XAML Power Toys was not necessary. We're not yet sure if there is something specific the XAML Power Toys are doing, or if any custom add-in will cause this issue.
Workaround: Remove the XAML Power Toys add-in from Visual Studio's options (Tools -> Options -> Environment -> Add-in/Macros Security)
Applies To: VS2008

Adding a new model to the Model Project
5. Recipe framework error when overridden model-file on disk (13322): When overriding a model-file on disk, the CreateModel recipe throws an exception.
Workaround: remove the original model from disk, and then generate a new one.
Applies To: VS2005
Working with the model designers

6. Right clicking on Host, Service Contract, or Data Contract designers causes a HRESULT EFAIL dialog (14523): After installation of the Web Service Software Factory, right clicking on the Host Explorer or Service or Data Contract designers causes a dialog with the text "HRESULT EFAIL has been returned on call to COM component" to appear. This means the DSLs have failed to register correctly.
Workaround: This is a know issue with the DSL installation. To fix this shutdown Visual Studio and manually run DEVENV.EXE /setup from the Visual Studio Command Prompt or re-install WSSF:ME in a machine with VS2005. This behavior was also observed in environments with both version of Visual Studio, 2005 and 2008.
Applies To: VS2005

7. If project is deleted and it has an entry in the Project Mapping Table file, an error is thrown (13974): If we unfold a WCF solution, create a DataContract Model, set the Project Mapping Table, delete the data contract project and add a data contract shape an error occurs. A similar issue occurs with other projects associated with Model element's in the Message contract, service contracts project.
Workaround: Remove first the project from the Mapping table, then the project from the solution, and finally assign another project to the deleted role.
Applies To: VS2005

8. Service Contract and Data Contract Models: "Type" type editor produces error (13637): The type editor for the Type field does not work properly if there is an unavailable project in the solution.
Workaround: Removing the projects resolves the issue. Ideally, the type filter should not attempt to query for types from unavailable projects.
Applies To: VS2005

9. Dialog error message on long names (13561): If the data contract name or any other element's name is more than 260 characters, a dialog error message is thrown. However on clicking on ok, no more warnings or error messages are shown. You are able to save or validate the model without any issues. Only on Generate code, the following error is shown: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
Workaround: Avoid long names on directories entries or items.
Applies To: VS2005, VS2008

10. User sees "cannot find schema" warning when working with the DSL models (13747): Warning 3 Cannot find a schema that defines target namespace 'http://schemas.microsoft.com/dsltools/ServiceContractDsl', schema validation skipped.
Workaround: This schema is for internal use of the factory, and it doesn’t affect any operation or code generation result.
Applies To: VS2005, VS2008

11. Cannot use any specialized collection while selecting types (12254): It is not allowed to select specialized collections from collection type.
Workaround: Customize the factory (using the source code provided) creating a new filter for the TypeBrowser editor capable of adding custom collections.
Applies To: VS2005, VS2008

12. A NullReferenceException is thrown when renaming a model project (14592): When you rename a model project, the Validate and ValidateAll commands on a service contract will throw a NullReferenceException without any further details.
NOTE: The null reference exception occurs on attempting to generate code, and on saving
Workaround: Open the underlying XML structure. Notice that data contract references include the name of the project instead of the GUID. After fixing those names, the models opened up fine.
Applies To: VS2005

13. "Custom tool failed" warning when working with the DSL models (13748): The custom tool 'ResXFileCodeGenerator' failed while processing the file 'Properties\Resources.resx'.
Workaround: None. It doesn’t affect any operation or code generation.
Applies To: VS2005, VS2008
Working with the Service Contract Model

14. Error Message Not Appropriate during validation of references to faults (13243): in a Service Contract Model, when you add a DataContractMessagePart or a DataContractFault, without reference the corresponding type, it throws the following error: "The element type has a reference to a data contract model with no implementation technology or project mapping table associated". Both Implementation technology and Project Mapping Table is set properly for Service Contract Model and Data Contract Model.
Workaround: Just references the corresponding type in the Message or the Operation.
Applies To: VS2005

15. Fault contract project reference not removed (12545): When you add a Fault Contract in OperationContract and generate code, Fault contract project reference is getting added in service contract project. When you remove the fault from OperationContract and generate the code again, Fault contract project reference is not removed from service contract project
Workaround: Remove the project manually.
Applies To: VS2005, VS2008

16. Weird behavior when no Service Role is present in Project Mapping Table (13321): When adding a Service-MEL to model with an associated Project Mapping Table that lacks a ServiceRole the model behaves weird. It gives an unhandled exception and fills up the error-list with 5 errors. When right-clicking the MEL (in order to remove it) the context menu is disabled and it adds 5 more errors in the error-list. When you click Ignore, the validation message is shown in the error list that the project doesn't have a service role, but this error window re-appears. When you click Retry, it hints user that a breakpoint occurred and it further makes the solution unstable. When you click Abort, the VS crashes and solution closes leading to data loss.
Workaround: Add manually the ServiceRole project in the Project Mapping Table.
Applies To: VS2005

17. Service Factory allows a Message Contract with IsWrapped="True" to have the same name as Data Contract Model (13675): A Message Contract with IsWrapped = "True" should not contain the same name as a Data Contract Model. If so the following exception will be thrown on hosting the Service:
An exception was thrown in a call to a WSDL export extension: System.ServiceModel.Description.DataContractSerializerOperationBehavior contract: <service contract name> ----> System.Xml.Schema.XmlSchemaException: The global element <Data Contract Model name> has already been declared.
Workaround: Elements from a Message Contract should not have the same name from their parent, even if they had different case.
Applies To: VS2005
Working with the Data Contract Model

18. Data Contract Model Primitive Collection is not having property 'IsNullable' in property window (11793): The type picker doesn’t allow selecting nullable types, and the model doesn’t have an IsNullable option.
Workaround: Generics are not supported directly. Because the type picker doesn’t allow selecting generics types, an alternative solution is to open the model with an XML Editor, and change itemType manually. Another more involved solution may be to update the TypeBrowser Filter in the package and allow generics.
Applies To: VS2005, VS2008

19. Unable to include specialized collection members (9584): Not able to select specialized collection like System.Collections.Specialized.StringDictionary for Datamembers
Workaround: create message contract containing Data Contract Model part with collections types
Applies To: VS2005, VS2008
Validating a model

20. Errors generated are not subsequently cleared when exception occurs (12611): If a scenario generates exception, then errors generated by such scenarios are being shown again for subsequent validations even if they are not relevant
Workaround: Clean the error list by running the build option in VS.
Applies To: VS2005, VS2008

21. Validation functionality not capturing case sensitive duplicate names (13567): Validation step is not capturing duplicate case-sensitive names between an element and its part name.
Workaround: We are doing case insensitive comparisons to support different languages
Applies To: VS2005, VS2008

22. Service Contract Model designer zooms out automatically on validation error (11836): When the user double-clicks on a validation error to locate the invalid model element, the designer zooms out to view the entire model.
Workaround: Zoom can be managed, by pressing simultaneously the keys “Ctrl+“ (for zoom in), or “Ctrl-“ (for zoom out).
Applies To: VS2005, VS2008
Working with XSD Messages

23. Missing validation across Data Contract Model names and types referenced in XML schemas (13473): When a XSD Message referenced type name conflicts with a Data Contract Model name, validation error is not provided. The code generation silently overwrites the older code.
Workaround: Any Data Contract shape created should not conflict with the XML schema types referenced in XSD Message contracts. The same should be provided as validation message.
Applies To: VS2005, VS2008

24. Code related errors and cannot use XML schemas in subfolders of the ‘Schemas’ folder (14084): Add any XSD to a subfolder of the schemas folder, and add XsdMessage with a reference to it and validate. Code related errors occur (sometimes when you validate the first time, sometimes the second time).
Workaround: Locate the schema files in the “Schemas “ folder or any other root folder.
Applies To: VS2005

25. Usability issue when Xml schema has type and no element with XML Serializer option on Service Contract Model (14085): If the XML schema has no top level element and only the type definition we are able to pick the type using type picker but on validation an error occurs.
Workaround: Add an XML schema with valid top elements.
Applies To: VS2005

26. Code is generated for all the elements in the XML schema (14162): Even if lower level elements are selected in an XML schema, all the TOP level elements code is also generated during the code generation.
Workaround: No workaround. All elements will be generated. You may manually remove any unused type after code generation.
Applies To: VS2005, VS2008
Removing model elements or models

27. Removal of model elements or model files do not warn user to cleanup artifacts (13670): Deleting model elements from a model or a model project itself does not warn the user to cleanup artifacts.
Workaround: The user should manually update the generated artifacts and re generated from the updated models.
Applies To: VS2005, VS2008
Creating implementation projects

28. Projects name prefix on unfolding WCF and ASMX implementation projects should not be ASMX or WCF (14498): When using ASMX or WCF as aliases for namespaces, if the prefix name for projects when unfolding these templates has .WCF. or .ASMX. in them a clash in namespaces occur and this results in compile issues.
Workaround: avoid using WCF or ASMX as prefix on implementation projects
Applies To: VS2005

29. ASMX/WCF Service Project Mapping Table template expansion throws error: Expand ASMXService Template for Long path (11809): When you give a long path like “C:\Documents and Settings\user\My Documents\Visual Studio 2005\Projects\sv1\sv2”, an error occurs when we unfold the template.
Workaround: Avoid using long paths. The whole path, plus the file name, shouldn’t be longer than 260 characters.
Applies To: VS2005, VS2008
Mapping models to projects

30. ProjectMapping.xml should be the file present in the solution folder only (13527): The Project Mapping Table property of Data Contract Model designer and Service Contract designers refer to Project Mapping Table definitions from files which are excluded from the solution.
Workaround: Avoid generating extra mapping tables.
Applies To: VS2005, VS2008

31. Project Mapping Table reference is not removed when project is overwritten (13242): if we create a solution "TestService", generate Project Mapping Table for projects on it, save and close the solution, create another solution "TestService" and overwrite the original solution Project Mapping Table file is still the file for the first solution.
Workaround: Clean up manually the Project Mapping Table or remove the file. A new one will be automatically will be generated by the package by using the populate project mapping table, or generating new ASMX o WCF Implementation Projects
Applies To: VS2005, VS2008

32. When Roles aren't populated in Project Mapping Table, multiple errors (duplicates) are being logged repeatedly on clicking the model (14049): exceptions are not thrown but errors get duplicated on every right click.
Workaround: Add the missing roles in the Project Mapping Table.
Applies To: VS2005, VS2008

33. "Populate Project Mapping Table" Recipe should not generate invalid Project Mapping Tables (10348): This is related to having a Project Mapping Table with the same role in different projects.
Workaround: A project may have one or more roles but each role should be assigned to one project in that Project Mapping Table.
Applies To: VS2005, VS2008

Translating messages
34. Translator - Cannot map nested Data Contract Model to Business E which refers to Data Contract Model (12682):
If we have a nested Data Contract Model A as follows
A
{
Property of Data Contract Model B
}
Business Entity as follows:
BEA
{
Property of Data Contract Model B
}
It should be possible to map the property B of A and BEA using the translator. However at present an error is shown while trying to perform the mapping.
Workaround: DataContract and BussinessEntity projects shouldn’t be referenced between each others. Redesign your model to avoid this scenario.
Applies To: VS2005

35. Translator: Mapping allowed for an integer element to nullable integer that leads to compile time error (12646): Compile time error occurs on the generated code while mapping integer element to nullable integer element.
Workaround: Avoid mapping nullable to non nullable elements.
Applies To: VS2005, VS2008

36. Classes defined in BusinessEntity project are not visible in Create Translator Wizard (12451): Reference to BusinessEntity project should be added automatically to the Service Implementation project so that mapping can be specified without manually adding references.
Workaround: If we add a BusinessEntity project as a reference to Service Implementation project then we are able to specify mapping.
Applies To: VS2005
Running code analysis rules

37. Binary installer throws error for run code analysis in VSTA (14273): If you are installing on Visual Studio Professional or if you are using the Architect edition of Visual Studio Team System, you will not be able to run the code analysis rules, even though you will see the option to do so.
Workaround: Integrated Code Analysis is only available on the full version of VS Team System. In order to run this in other VS versions, get the VS SDK that comes with FxCop tool and update the FxCop API references in the code analysis projects (“WCF Semantic CodeAnalysis” or “WCF Security CodeAnalysis” projects) and run the code analysis from the FxCop tool specifying the updated rules assemblies.
Applies To: VS2005, VS2008

38. Code analysis did not validate service contract and binding (12627): When a service is exposed using basicHttpBinding and the sessionmode of service contract is defined to Required, code analysis warning specified in the acceptance criteria of the repro steps is not logged when we run code analysis.
Workaround: There is no built-in rule for this scenario. You may add a custom rule to the semantic project “WCF Semantic CodeAnalysis” or Follow the guidelines documented in WCF.
Applies To: VS2005

39. Code analysis doesn't work in VS Pro while running recipe (14210): Binary installer in VS-Pro throws errors on executing recipe 'Run WCF Code Analysis'.
Workaround: This options runs only in Team System Edition. Read (14273).
Applies To: VS2005, VS2008

40. WCF Semantic Validation : Operation with OneWay and Async set to true is not validated thru semantic validation (13843): Operations with Oneway property and async property set to true is not semantically validated
Workaround: These rules are not included in the semantic code analysis. Follow the guidelines documented in WCF.
Applies To: VS2005, VS2008

41. Code Analysis Projects are included but don't compile with VS Standard Edition (13669): VS 2005 Standard Edition does not have FxCop assemblies and, thus, cannot build the Analysis projects in the GP.
Workaround: This options runs only in Team System Edition.
Applies To: VS2005, VS2008

Working with the Host Model
42. Client Proxy generation works only with Proxy endpoint connector (13718): It is not possible to generate client proxies without a proxy endpoint connector which means that the client proxy generation will work only for local services and not if we want to generate a client proxy for a remote service. Next and Finish button are disabled
Workaround: Add an endpoint connector and try generating the proxy again.
Applies To: VS2005

43. On deleting a Client Application on the Host Explorer the Host Application becomes invisible (14503): Deleting a Client Application in the Host Explorer, makes the Host Application invisible.
Workaround: The Host Application is again visible when we click on the topmost node "Host Model"
Applies To: VS2005

44. Default values for Service Address and Service Reference Name not present while adding the “WCF Service Reference” through the Proxy in Client Application (13712): While giving the names of the models (for instance, in Russian, giving the names like ‘Картинки’) the file is saved as Unicode and the following scenario is found:
In Host Model, default Service Address and Service Reference Name is not present while adding the “WCF Service Reference” (by right click of Proxy) for a Client Application (before adding the “Proxy end Point Connector”).
Workaround: Service Factory has not been 100% tested to see if it is localizable / Globalization ready. However, most recipes should work fine.
Applies To: VS2005, (VS2008-Not 100% tested with Unicode)

45. Issues with invalid project reference file to a host object (14157): When we try to add a non- host project as reference to any host object in a host model, no validation error messages are thrown on right click.
Workaround: No workaround. The package doesn’t validate if the selected project is a host project. Just change the selected project, for the correct one.
Applies To: VS2005, VS2008

46. Host Model project references lost when relocating source code (15173): After moving the solution from one place to another, the reference to the old host project will persist.
Workaround: The reference to the old project path should be updated by selecting the new location of the host project. Notice that this will also apply to Client Application project location.
Applies To: VS2008

Generating code from a model
47. Inconsistent behavior with the generate code option on a collection data contract shape (11389): If you right click on a collection data contract which has a data contract specified as an element of a collection and generate code, generated code does not compile since the code for the contained data contract is not generated. This is not the behavior with aggregation relationships between data contracts in which case we get valid code.
Workaround:
  • Its possible to do the following:
  • Create a data contract shape Data Contract Model1
  • Create another data contract shape Data Contract Model2
  • Aggregate Data Contract Model1 and Data Contract Model2
  • Right click on the container data contract and choose generate code
  • Generated code complies successfully
  • Its possible to do the following but generate code does not compile:
  • Create a DataContract customer with field customerID of primitive type
  • Create a Collection data contract with Data contract type set to DataContract Customer and base collection type as List
  • Right click on the collection data contract and generate code
  • Code does not compile since only code for the collection is generated. Since the code for the data contract is not generated the compile issue occurs.
  • To solve this, use the steps described above.
Applies To: VS2005, VS2008

48. Inconsistency with file name created with ASMX and WCF extenders for ServiceContracts (13966): If you generate code for a Service Contract from one technology and after that you switch to other technology, two different Service Contract files will be generated (one with ‘I’ prefix and the other without) creating a clash of interfaces.
Workaround: Remove any previous Service Contract file after changing technologies.
Applies To: VS2005, VS2008

49. Data Contract Model: Generating a data contract with two data elements that only differ by the case of the first letter generates code that does not compile (9708): if we add two elements with the same name, but different case, it validates correctly. When we generate code, generated code doesn’t build correctly.
Workaround: Avoid using elements with same name, even if they have different case.
Applies To: VS2005, VS2008

50. Doesn’t clean the Service Contract project when changing the extender (11207): If you choose WCF extender for a Service Contract Model, generate code and then switch to ASMX extender and generate code again references to WCF specific assemblies still exist on the Service Contract project - this is redundant behavior. Similar issue occurs in the reverse scenario - choose ASMX extender first and generate code and then switch to WCF extender and generate code.
Workaround: After changing the extender, the Service Contract file must be cleaned up manually.
Applies To: VS2005, VS2008

51. Expose Host code generation produces inconsistent results when Service Implementation is not generated (13757): Expose service will fail due inability to resolve CLR type of service implementation.
Workaround: Generate the code, for the service model first.
Applies To: VS2005, VS2008

52. Generated code folder for client project is not used, proxy code is generated in the service reference folder (13759): Currently generate proxies in the ServiceReference folder and not in the generated code folder.
Workaround: None. It doesn’t affect any operation or code generation.
Applies To: VS2005, VS2008

53. When Data Contract shapes are aggregated, the message provided after code generation is incorrect (11317): When Data Contract Model members are aggregated and code generated, the information message provided to the user denotes an incorrect number of objects generated.
Workaround: None. This is only a descriptive issue but the generated artifact number is correct.
Applies To: VS2005

54. Code generation closes the existing opened CS files (14151): Code generation automatically closes the existing opened CS files.
Workaround: No workaround. It doesn’t affect any operation or code generation.
Applies To: VS2005, VS2008

55. Generated ServiceImplementation code does not throw –not implemented Exception– (12258): In v3, Generated Code for Service Implementation does not throw not implemented Exception .The code returns null. In previous versions of the factory, the generated code throws an Exception.
Workaround: In WSSF:ME, the package returns nulls instead of an exception, it’s up to the user override the operation.
Applies To: VS2005, VS2008

56. Generated code for the FaultContract project does not see DataContract types: Generated Code for FaultContract with aggregated DataContracts will generate code without a reference to the DataContract project and therefore it won’t compile.
Workaround: There is a fix posted in this thread: http://www.codeplex.com/servicefactory/Thread/View.aspx?ThreadId=29740
Applies To: VS2005, VS2008

Using other factories with the Service Factory
57. Compatibility difference between WSSF:ME and Repository Factory - Generated code is not generated at 'Generated code' folder (14099): Generated code option in Repository factory generates code in root folder not in the 'Generated code' folder.
Workaround: It is a mismatch between these two guidance packages.
Applies To: VS2005, VS2008

Building the factory source code
58. Solution does not open when installing source code msi (11384): If we install on a folder like “c:\WSSF” or “c:\Build69” there are no issues. If we install on a subfolder like “c:\source\build69” the solution file generated is an xml file and the actual solution file goes into “c:\”.
Workaround: It’s possible to overwrite the XML file (which appears to have a .sln extension) with the one in the c drive and then proceed. It does happen in XP and inconsistently on other OS.
Applies To: VS2005

59. Source code installer not generating msi on first build (14234): Source code is not generating on the first build in release mode. If we do rebuild (2nd or 3rd time) on installer project alone then it is generating.
Workaround: Installer is generated only while doing build on the Installer project, after building the whole solution.
Applies To: VS2005, VS2008

60. FxCop unit tests are now included in the installed solution which will break VS Pro builds (12252): If we add them then the SLN.CONFIG includes them and they'll get added to the deployed solution but this will break VS Pro installations as the projects reference some of the FxCop (Static Analysis) DLLs that are not installed by Pro.
Workaround: Remove the projects from the solution if using VS Pro, or install the source code without the unit tests (VS2008).
Applies To: VS2005, VS2008

General Issues
61. Can't create solution in VS 2008 version of SF.
After successfully installing the prerequisites and the VS 2008 binary version of the Service Factory - Modeling Edition, you get the following exception when I try to create a modeling solution:
Microsoft.Practices.RecipeFramework.ActionExecutionException: An exception occurred during the binding of reference or execution of recipe CreateSolution. Error was: Action CreateMappingFileAction failed to execute:
Object reference not set to an instance of an object..
Workaround: Setting the default XML editor in VS 2008 back to the default VS XML editor. If you had set the default XML editor to Expression Web or other XML Editor, when the create solution recipe ran Expression Web would automatically start and then the recipe would abort with the above exception. As soon as you set the XML editor back to the default in VS then the create solution recipe completed without error.
For further details read: http://servicefactory.codeplex.com/Thread/View.aspx?ThreadId=21659
Applies To: VS2008

62. A couple of our advisors have recently run into a issue. If you have the XAML Power Toys installed, it can cause your Service Factory installation to completely stop working.
Workaround: Removing the XAML Power Toys from the Visual Studio add-ins (and restarting VS) fixed the problem - uninstallation of the XAML Power Toys is not necessary.
Applies To: VS2008

Last edited Feb 3, 2010 at 10:10 PM by donsmith, version 9

Comments

johnqxu Mar 19 at 5:40 PM 
I would like to see the issue related to WSSF 2010 which is not listed here. I am trying to open an exisitng solution generated from WSSF 2008 but WSSF 2010 diplay error could not load .ssfproduct.

How can resolve this issue?