Error service Microsoft. Practices. compositeweb. Interfaces. isitemapbuilderservice is not available in

1. Install guidanceautomationtoolkitforvs2008.msi and wcsf to obtain projects created by others from VSS. Because others' installation paths may be different from their own

When you add business module, some Enterprise Library DLL files cannot be found. At this time, only the Enterprise Library DLL files are successfully added.

Moduleinitializer/controller/defaultviewpresenter and their respective interface files. However, the webform module does not successfully add files and compilation fails.

To solve this problem:
1). In the simplest way, You can manually create a folder library under the root directory of solution, copy the DLL of several enterprise libraries used to the bottom, and copy the unfinished business

Module deletion, which can be solved after reconstruction.
2) manually add the required Enterprise Library DLL references to the buiness module based on the business module that has not been created, and add them to the websites side for addition.

For a folder with the same name as business module, right-click the folder and execute Web Client factory --> add page (with presenter) C # To give the page a name.

If userlist. aspx is used, the userlistpresenter and iuserlistview classes are automatically added to the Views folder of the business module.

Of course, the page code will automatically inherit iuserlistview. The compilation is successful, but an error occurs during running.
Error message:
Service Microsoft. Practices. compositeweb. Interfaces. isitemapbuilderservice is not available in the current context.
After comparing the projects that can run normally, we found that a web. config file is missing in the sub-folder with the same name as the business module under websites.

As follows:
<Configuration>
<Configsections>
<Sectiongroup name = "compositeweb">
<Section name = "modules" type = "Microsoft. Practices. compositeweb. configuration. modulesconfigurationsection,

Microsoft. Practices. compositeweb "/>
<Section name = "Authorization"

Type = "Microsoft. Practices. compositeweb. configuration. authorizationconfigurationsection,

Microsoft. Practices. compositeweb "/>
</Sectiongroup>
</Configsections>
<Compositeweb>
<Modules>
<Module name = "usermaint" assemblyname = "usermaint" virtualpath = "~ /Usermaint ">
<Dependencies>
<Dependency module = "shell"/>
</Dependencies>
</Module>
</Modules>
<Authorization>
<! -- Add your own view-Rule mappings here:
E.g .:
<Rule url = "~ /Helloworld/default. aspx "rule =" allowaccesshelloworlddefaultview "/>
-->
</Authorization>
</Compositeweb>
<Appsettings/>
<Connectionstrings/>
<System. Web/>
</Configuration>

Modify <Module name = "usermaint" assemblyname = "usermaint" virtualpath = "~ /Usermaint ">