FIX: Web Setup Project Includes .vsdisco Files in Deployment Files (319968)



The information in this article applies to:

  • Microsoft Visual C++ .NET (2002)

This article was previously published under Q319968

SYMPTOMS

When you deploy a Managed Extensions for C++ Web Service by using a Web Setup project, the .vsdisco file that is associated with the XML Web Service project is included in the Content files group. Consequently, the .vsdisco file is deployed to a production server. This is a security risk.

RESOLUTION

To have control over which XML Web services clients can discover, use only dynamic discovery on development Web servers. When you deploy an XML Web Service to a production Web server, create a static discovery file (.disco) instead of a dynamic discovery file (vdisco) for those XML Web services that you want to permit clients to discover.

To use the ExcludeFilter property to remove the .vsdisco file from the Outputs property list, follow these steps:
  1. In Solution Explorer, click the Content files in your Web Setup project to display the properties for the files.
  2. In Properties, click ExcludeFilter.
  3. Click Add Filter, and then type *.vsdisco. Click OK.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Microsoft Visual C++ .NET (2003).

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create a new Managed Extensions for C++ Web Service project.
  2. Add a Web Setup project to the solution.
  3. On the File System tab, right-click the Web Application Folder, point to Add, and then click Project Output.
  4. In the Add Project Output Group window, click Content Files, and then click OK.
  5. Click to select the Content files in Solution Explorer to display the properties.
  6. In Properties, click Outputs to view the list of output files.

REFERENCES

For more information, visit the following articles in the Microsoft Developer Network (MSDN) Web sites:

Modification Type:MajorLast Reviewed:4/11/2003
Keywords:kbfix kbbug kbIDEProject kbnofix KB319968